Repository navigation
Version 0.2.0 and readable package versions - #9
Merged
Merged
Conversation
Tagged releases now build as the bare version (ringzero-security_0.2.0_amd64.deb); the tag must match VERSION. Builds from main carry +main.<run number>, the same on both architectures, instead of a per-runner timestamp and commit. Local builds keep a +local timestamp so reinstalls still upgrade. 0.2.0 also sorts above the 0.1.4.0 packages the website served before.
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.
Package versions were
0.1.0+20261011084520.g29111bd8: a UTC build time plus the commit, different on arm64 and amd64 because each runner used its own clock.v0.2.00.1.0+<time>.g<sha>0.2.0latest)0.1.0+<time>.g<sha>0.2.0+main.<run>./build-deb.sh0.1.0+<time>.g<sha>0.2.0+local.<time>VERSION, or a modified tree on a tag, fails the build./usr/lib/ringzero/BUILDandrz version.After merging,
git tag v0.2.0 && git push origin v0.2.0publishes the first clean release.