Conversation
Member
Author
|
@Cinnazeyy what do you think of using version ranges? I have a split options, on one side it's nice to automatically get new fixes etc. At the same time it might also pull things in we don't want. Even through it should be save for libs which uses sem ver. Plugins might be a problem trough. Biggest downside is that builds are not reproducable anymore with that, so maybe no that good for the plugins itself, but only for the libs. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
build(gradle): update dependencies to flexible versions and upgrade Gradle to 9.5.1
Main dependency which needed an update was XSeries in the alpslib, that errored out otherwise.