-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Bump to v0.37.2 #4492
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
8000
Jump to bottom
Merged
Merged
Bump to v0.37.2 #4492
Conversation
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
IGI-111
approved these changes
Apr 24, 2023
rostyslavtyshko
approved these changes
Apr 24, 2023
This release includes quite a few breaking changes (including Mohammad's storage key refactor) and likely should be rolled out under a new minor release, 0.38.0. I'm unsure if we have the ability to yank 0.37.2, but if we can we should and re-release as 0.38.0 to avoid mysteriously breaking things for users who d epend on 0.37.1. |
It looks like yanking might not be an option, so we might need to:
|
mitchmindtree
added a commit
that referenced
this pull request
Apr 25, 2023
…nges Aimed at addressing the following comment: #4492 (comment) Currently our bot doesn't make it easy to yank existing releases. Here we just republish 0.37.1 as 0.37.3 to ensure users updating their sway repo deps don't consume the breaking changes accidentally included in 0.37.2.
mitchmindtree
added a commit
that referenced
this pull request
Apr 25, 2023
See here: #4492 (comment) This follows a re-release of 0.37.1 as 0.37.3: https://github.com/FuelLabs/sway/releases/tag/v0.37.3 The outcome of all this is that ideally, users previously on 0.37.1 will now pull 0.37.3 next time they run `cargo update` and will not encounter any breakage. Those ready to update can now point to 0.38.0.
mitchmindtree
added a commit
that referenced
this pull request
Apr 25, 2023
See here for context: #4492 (comment) This follows a re-release of 0.37.1 as 0.37.3: https://github.com/FuelLabs/sway/releases/tag/v0.37.3 The outcome of all this is that ideally, users previously on 0.37.1 will now pull 0.37.3 next time they run `cargo update` and will not encounter any breakage. Those ready to update can point to 0.38.0 after this is published. Also runs `cargo update` in order to update deps to their latest patch release. --------- Co-authored-by: Joshua Batty <joshpbatty@gmail.com>
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.
Waiting for:
fix broken installation url, typo #4488we can get this later on it is not urgent.