-
Notifications
You must be signed in to change notification settings - Fork 11
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): Non-AWS dependency updates #199
Closed
Closed
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
gu-scala-steward-public-repos
bot
changed the title
Non-AWS dependency updates
chore(deps): Non-AWS dependency updates
Nov 9, 2023
rtyley
added a commit
that referenced
this pull request
Dec 7, 2023
Looking at #199, we can see that Scala Steward is trying to upgrade Play version numbers in ways that aren't correct: https://www.playframework.com/documentation/3.0.x/Migration30#Changed-groupId This is possibly related to: scala-steward-org/scala-steward#3191 scala-steward-org/scala-steward#3191 (comment) To fix this up, for now we'll ignore Play updates here, as in guardian/play-secret-rotation@607802e
rtyley
reviewed
Dec 7, 2023
val V29 = PlayVersion("29", "com.typesafe.play", "2.9.0", supportsScala3 = true) | ||
val V28 = PlayVersion("28", "com.typesafe.play", "2.8.21") | ||
val V29 = PlayVersion("29", "com.typesafe.play", "3.0.0", supportsScala3 = true) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The upgrade for V29
from 2.9.0 to 3.0.0 is wrong here - we don't want it to jump major versions.
See #206
Closing because the Play V29 upgrade from 2.9.0 to 3.0.0 is wrong - have raised #206, and the next Scala Steward job should hopefully not attempt that particular upgrade. |
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.
About this PR
Updates:
directory_v1-rev20230516-2.0.0
todirectory_v1-rev20231113-2.0.0
1.19.0
to1.20.0
32.1.1-jre
to32.1.3-jre
2.8.20
to2.8.21
2.9.0
to3.0.0
β2.8.20
to2.8.21
2.9.0
to3.0.0
β2.8.20
to2.8.21
2.9.0
to3.0.0
β2.13.11
to2.13.12
3.2.16
to3.2.17
2.9.0
to2.10.0
3.9.21
to3.10.0
Usage
β Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
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!
β Adjust future updates
Add these to your
.scala-steward.conf
file to ignore future updates of these dependencies:Or, add these to slow down future updates of these dependencies: