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

Update snakeyaml-engine to 2.8 #150

Merged
merged 1 commit into from
Sep 18, 2024
Merged

Update snakeyaml-engine to 2.8 #150

merged 1 commit into from
Sep 18, 2024

Conversation

hnaderi
Copy link
Owner

@hnaderi hnaderi commented Sep 18, 2024

About this PR

📦 Updates org.snakeyaml:snakeyaml-engine from 2.7 to 2.8

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

docs/logo.svg
modules/jsyaml/.js/package-lock.json
⚙ Adjust future updates

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

updates.ignore = [ { groupId = "org.snakeyaml", artifactId = "snakeyaml-engine" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.snakeyaml", artifactId = "snakeyaml-engine" }
}]
labels: library-update, old-version-remains, commit-count:1

@mergify mergify bot merged commit 8ab464a into main Sep 18, 2024
23 checks passed
@mergify mergify bot deleted the update/snakeyaml-engine-2.8 branch September 18, 2024 01:06
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