feat(foundryup): default base-foundryup to v1.1.0 (effectively final Beryl)#46
Merged
Merged
Conversation
cafba17 to
b42b919
Compare
b42b919 to
dcf4342
Compare
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
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.
What
Default bare
base-foundryup(no version arg) tov1.1.0instead ofv1.1.0-rc.19.Why
v1.1.0(final Beryl) is published and validated, and supersedes the rc. Pinning the default to it means the one-liner install serves the final release. Rolling builds remain available viabase-foundryup --install nightly.Validation
The published
v1.1.0tarballs were verified via the real install flow (base-foundryup --install v1.1.0) +base-forge testcalling a Base precompile:(linux amd64 / alpine / Windows are covered by the per-platform CI smoke matrix, #44.)