Update sbt-mdoc to 2.7.2 #3978
Update sbt-mdoc to 2.7.2 #3978
Conversation
There was a problem hiding this comment.
Summary of Changes
Hello @xerial-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request is an automated dependency update, initiated by Scala Steward, to upgrade the sbt-mdoc plugin to its latest patch version. This update aims to incorporate any recent bug fixes or minor enhancements from the upstream mdoc library into the project's build configuration.
Highlights
- Dependency Update: This pull request updates the
sbt-mdocplugin from version2.7.1to2.7.2.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
| @@ -37,7 +37,7 @@ addSbtPlugin("org.scala-native" % "sbt-scala-native" % "0.5.8") | |||
| addSbtPlugin("com.github.sbt" % "sbt-dynver" % "5.1.1") | |||
|
|
|||
| // Documentation | |||
| addSbtPlugin("org.scalameta" % "sbt-mdoc" % "2.7.1") | |||
| addSbtPlugin("org.scalameta" % "sbt-mdoc" % "2.7.2") | |||
There was a problem hiding this comment.
Updating the sbt-mdoc version is a good practice to keep dependencies up-to-date and benefit from the latest features and bug fixes. However, it's crucial to verify compatibility with the existing codebase and other dependencies. Consider adding a note to verify compatibility after the update.
addSbtPlugin("org.scalameta" % "sbt-mdoc" % "2.7.2") // Verify compatibility after update
About this PR
📦 Updates org.scalameta:sbt-mdoc from
2.7.1to2.7.2📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a
.scala-steward.conffile.Have a fantastic day writing Scala!
🔍 Files still referring to the old version number
The following files still refer to the old version number (2.7.1).
You might want to review and update them manually.
⚙ Adjust future updates
Add this to your
.scala-steward.conffile to ignore future updates of this dependency:Or, add this to slow down future updates of this dependency: