[2.9.x] sbt 1.10.0 (backport #12628) by @mkurz #12629
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
(cherry picked from commit 77721ef)
Merged
mkurz
changed the title
mkurz
approved these changes
May 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I didn't upgrade sbt in the 3.0.x branch before the 3.0.3 release just to keep things safe, in case 1.10.0 would break stuff like it happend with sbt 1.9.5 once.
For next 3.0.x release it should be ok to now upgrade to sbt 1.10.0, given 3.0.4 is a couple of weeks away and if sbt 1.10.0 has major issues I guess they would surface until then.
This is an automatic backport of pull request #12628 done by Mergify.