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

chore(deps): update dependency com.esotericsoftware:kryo to v5.6.1 #1598

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 7, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.esotericsoftware:kryo 5.6.0 -> 5.6.1 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/kryo5.version branch 3 times, most recently from eae4361 to 14c82d1 Compare October 9, 2024 09:50
@nielsbasjes
Copy link
Owner

This Kryo version is bad.
EsotericSoftware/kryo#1134

@nielsbasjes nielsbasjes closed this Oct 9, 2024
Copy link
Contributor Author

renovate bot commented Oct 9, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (5.6.1). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/kryo5.version branch October 9, 2024 15:22
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