Update sbt-ci-release to 1.7.0

[scala-steward]

About this PR

📦 Updates com.github.sbt:sbt-ci-release from 1.6.1 to 1.7.0

📜 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.conf file.

Have a fantastic day writing Scala!

🔍 Files still referring to the old version number

The following files still refer to the old version number (1.6.1).
You might want to review and update them manually.

notes/1.7.markdown

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "com.github.sbt", artifactId = "sbt-ci-release" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.sbt", artifactId = "sbt-ci-release" }
}]

^{labels: sbt-plugin-update, early-semver-minor, semver-spec-minor, old-version-remains, commit-count:1}

Summary by CodeRabbit

• Chores
  • Updated the version of the sbt-ci-release plugin to enhance build and release processes.

[coderabbitai]

Walkthrough

The changes in this pull request involve updating the version of the sbt-ci-release plugin in the project/plugins.sbt file from version 1.6.1 to 1.7.0. No other modifications were made to the file, which retains its existing plugins and resolver configurations.

Changes

File	Change Summary
project/plugins.sbt	Updated sbt-ci-release plugin version from 1.6.1 to 1.7.0.

Poem

In the garden where plugins play,
A new version hops in today.
From 1.6.1 to 1.7.0,
A leap of joy, oh what a show!
With every change, we grow and cheer,
For better builds, we hold so dear! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between a740548 and 15b12ba.

📒 Files selected for processing (1)

• project/plugins.sbt (1 hunks)

🧰 Additional context used

🔇 Additional comments (1)

project/plugins.sbt (1)

12-12: LGTM: Version update correctly implemented.

The sbt-ci-release plugin has been successfully updated from version 1.6.1 to 1.7.0 as intended.

To ensure a smooth transition, please:

1. Review the release notes for any breaking changes or new features that might affect your build process.
2. Check other files in the project that might still reference the old version number (1.6.1), particularly notes/1.7.markdown as mentioned in the PR description.

Would you like assistance in creating update scripts for these references or opening a GitHub issue to track this task?

✅ Verification successful

Verification Complete: No remaining references to version 1.6.1 found in the codebase.

• Only notes/1.7.markdown contains references to version 1.6.1, which is appropriate for release notes.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Search for references to the old version number (1.6.1) in the project

echo "Files still referencing version 1.6.1:"
rg --type-not sbt "1\.6\.1"

echo "\nChecking specifically for notes/1.7.markdown:"
cat notes/1.7.markdown 2>/dev/null || echo "File not found: notes/1.7.markdown"

Length of output: 1876

---

Script:

#!/bin/bash
# Description: Search for references to the old version number (1.6.1) in the project, excluding .sbt files

echo "Files still referencing version 1.6.1:"
rg --glob '!*.sbt' "1\.6\.1"

echo "\nChecking specifically for notes/1.7.markdown:"
cat notes/1.7.markdown 2>/dev/null || echo "File not found: notes/1.7.markdown"

Length of output: 1916

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.