Update sbt-buildinfo to 0.13.1

[scala-steward]

About this PR

📦 Updates com.eed3si9n:sbt-buildinfo from 0.13.0 to 0.13.1

📜 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!

⚙ Adjust future updates

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

updates.ignore = [ { groupId = "com.eed3si9n", artifactId = "sbt-buildinfo" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.eed3si9n", artifactId = "sbt-buildinfo" }
}]

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

Summary by CodeRabbit

• Bug Fixes
  • Updated the sbt-buildinfo plugin to version 0.13.1, which may include bug fixes or minor enhancements.

[coderabbitai]

Walkthrough

The pull request updates the version of the sbt-buildinfo plugin in the project/plugins.sbt file from 0.13.0 to 0.13.1. This change is a minor version increment, indicating a potential bug fix or minor enhancement, while all other plugin declarations and resolver configurations remain unchanged.

Changes

File	Change Summary
project/plugins.sbt	Updated sbt-buildinfo plugin version from 0.13.0 to 0.13.1

Possibly related PRs

• Update sbt-buildinfo to 0.13.0 #1284: This PR updates the sbt-buildinfo plugin from version 0.12.0 to 0.13.0, which is directly related to the main PR that updates the same plugin from 0.13.0 to 0.13.1.

🐰 In the garden, I hop with glee,
A plugin's version, oh so free!
From 0.13.0 to 0.13.1,
A tiny leap, but oh what fun!
With every change, we grow and play,
In code and hops, we find our way! 🌼

---

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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 15176e5 and e3439e3.

📒 Files selected for processing (1)

• project/plugins.sbt (1 hunks)

[coderabbitai]

💡 Codebase verification

Version 0.13.1 exists but hasn't been released yet

The PR is updating to version 0.13.1, which exists as a tag (v0.13.1) in the repository but hasn't been officially released yet. The latest official release is still 0.13.0. It's recommended to wait for the official release before updating.

• The tag v0.13.1 was created recently (commit 07337b5)
• The latest GitHub release is still v0.13.0
• Using an unreleased version could lead to potential issues

🔗 Analysis chain

LGTM! Safe patch update for sbt-buildinfo.

The update from 0.13.0 to 0.13.1 is a patch version increment, indicating only backwards compatible bug fixes. This is a safe change that shouldn't impact the build process.

Let's verify this is the latest stable version:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the latest version of sbt-buildinfo
# Expected: Should show 0.13.1 as the latest stable version

# Check the latest release tag
gh release list --repo sbt/sbt-buildinfo --limit 1

Length of output: 95

---

Script:

#!/bin/bash
# Let's verify if there are any newer releases or tags that might not be marked as releases
gh api repos/sbt/sbt-buildinfo/tags --jq '.[0:3] | .[] | {name, commit: .commit.sha}'

# Also check if there are any recent commits that might indicate a newer version
gh api repos/sbt/sbt-buildinfo/commits --jq '.[0:3] | .[] | {sha: .sha, date: .commit.author.date, message: .commit.message}'

Length of output: 867