chore(release): publish v0.130.0 as the first stable MVP - #77
Merged
Merged
Conversation
Record the qualified MVP scope and preserve the historical prerelease. Keep the CI-qualified, PRE-tested kernel unchanged.
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.
Scope
Promote the documented MVP scope to stable source release v0.130.0. Update only the version label and user-facing release/usage documentation. Preserve the historical prerelease and its limitations.
Kernel, build and test-runner sources remain identical to f6e2135, which passed MVP CI and four valid four-node PRE correctness samples. Performance remains report-only. No production-HA, crash-recovery or independent-host shared-LUN certification is claimed.
Verification
Local version, relative links, shell syntax, initializer SHA-256, release-note privacy and whitespace checks passed. Full Fast CI and MVP release CI must pass on the exact candidate and final tagged commit. No CI waiver or branch-protection change.
The maintainer approved a one-time human-approval bypass for this release after complete CI is green.