chore: version the fork as 0.5.4-rigel.1 (RIG-3585) - #11
Draft
rigel-mintaka wants to merge 1 commit into
Draft
rigel-mintaka wants to merge 1 commit into
rigel-mintaka wants to merge 1 commit into
Conversation
The fork sat at 0.5.3 while carrying upstream v0.5.4's content plus fork-local changes, so `jj-vine --version` under-reported the running build. Move the fork's version line onto upstream's 0.5.4 base with a `-rigel.N` prerelease suffix, the fleet's convention for fork builds: it signals 'post-0.5.4 upstream base, with local patches' without claiming to be upstream's 0.5.4 release. Bumps Cargo.toml and the jj-vine entry in Cargo.lock. `jj-vine --version` now reports 0.5.4-rigel.1, and orion's nix pin (jj-vine.nix version + both lockfiles) can mirror it truthfully. Spec-impact: none. Refs RIG-3585 Co-authored-by: Matt Wilkinson <matt@rigel.build>
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.
The fork sat at 0.5.3 while carrying upstream v0.5.4's content plus fork-local changes, so
jj-vine --versionunder-reported the running build. Move the fork's version line onto upstream's 0.5.4 base with a-rigel.Nprerelease suffix, the fleet's convention for fork builds: it signals 'post-0.5.4 upstream base, with local patches' without claiming to be upstream's 0.5.4 release.Bumps Cargo.toml and the jj-vine entry in Cargo.lock.
jj-vine --versionnow reports 0.5.4-rigel.1, and orion's nix pin (jj-vine.nix version + both lockfiles) can mirror it truthfully.Spec-impact: none. Refs RIG-3585
Co-authored-by: Matt Wilkinson matt@rigel.build