chore: bring v0.14.0 alpha changes to next#1815
Merged
Conversation
Co-authored-by: Claude (Opus) <noreply@anthropic.com>
Mirko-von-Leipzig
approved these changes
Mar 20, 2026
Collaborator
Mirko-von-Leipzig
left a comment
Mirko-von-Leipzig
left a comment
There was a problem hiding this comment.
It makes sense to keep using next as alphas/betas/rc base until we make the first actual release.
Contributor
Author
|
Updated order of steps:
|
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
2 participants
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 realized that since
nextis still pointing toalphareleases, we can still deploy the latest state of node'snextto devnet. Steps:alphabranch changes tonextnextback intoalphaalpha, release the newalpha.8crates and then deploy that to devnet.The advantage of doing this over releasing straight from
alphais thatalphadoesn't have some useful changes likevalidator bootstrapcommand (which actuallymiden-genesisbinary assumes, and I forgot about this when changing the PR base fromnexttorelease/0.14-alpha)