Skip to content

build(deps): Update scalameta, semanticdb-metap, ... from 4.17.0 to 4.17.3#8734

Open
scala-steward wants to merge 1 commit into
scalameta:mainfrom
scala-steward:update/scalameta-4.17.3
Open

build(deps): Update scalameta, semanticdb-metap, ... from 4.17.0 to 4.17.3#8734
scala-steward wants to merge 1 commit into
scalameta:mainfrom
scala-steward:update/scalameta-4.17.3

Conversation

@scala-steward

@scala-steward scala-steward commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

About this PR

📦 Updates

from 4.17.0 to 4.17.3

📜 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 (4.17.0).
You might want to review and update them manually.

website/blog/2026-07-23-osmium.md
⚙ Adjust future updates

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

updates.ignore = [ { groupId = "org.scalameta" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta" }
}]
labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:semver-spec, old-version-remains, commit-count:1

Summary by CodeRabbit

  • Chores
    • Updated the bundled Scalameta tooling to version 4.17.3.

@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Updates the scalameta version constant in project/V.scala from 4.17.0 to 4.17.3.

Changes

Scalameta version update

Layer / File(s) Summary
Update scalameta version constant
project/V.scala
Object V now defines scalameta as version 4.17.3 instead of 4.17.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains

Suggested reviewers: tgodzik, github-actions

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the dependency version bump from 4.17.0 to 4.17.3 and matches the PR changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@project/V.scala`:
- Line 79: Update the version reference in website/blog/2026-07-23-osmium.md
from 4.17.0 to 4.17.3 so it matches the scalameta value in V.scala, unless that
reference is intentionally historical; in that case, clearly label it as
historical context.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e528a9b1-503f-46f3-8ee9-ff7867baf824

📥 Commits

Reviewing files that changed from the base of the PR and between 0116337 and 1437fec.

📒 Files selected for processing (1)
  • project/V.scala

Comment thread project/V.scala
val scalafmt = "3.11.4"

val scalameta = "4.17.0"
val scalameta = "4.17.3"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Update the stale blog reference.

website/blog/2026-07-23-osmium.md still references 4.17.0, so the version bump leaves user-facing documentation inconsistent. Update it to 4.17.3, or explicitly preserve it as historical context.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@project/V.scala` at line 79, Update the version reference in
website/blog/2026-07-23-osmium.md from 4.17.0 to 4.17.3 so it matches the
scalameta value in V.scala, unless that reference is intentionally historical;
in that case, clearly label it as historical context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant