Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): Update scalameta, semanticdb-scalac, ... from 4.7.7 to 4.7.8 #5299

Merged
merged 2 commits into from Jun 2, 2023

Conversation

scalameta-bot
Copy link
Contributor

Updates

from 4.7.7 to 4.7.8.
GitHub Release Notes - Version Diff

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

website/blog/2023-04-21-aluminium.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

@tgodzik tgodzik enabled auto-merge (rebase) June 2, 2023 07:38
auto-merge was automatically disabled June 2, 2023 07:49

Rebase failed

@tgodzik tgodzik merged commit f10f326 into main Jun 2, 2023
21 of 23 checks passed
@tgodzik tgodzik deleted the update/scalameta-4.7.8 branch June 2, 2023 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants