Repository navigation
feat(results): allocate semantic editions and release dates - #294
Open
lanyue-llk wants to merge 1 commit into
Open
lanyue-llk wants to merge 1 commit into
lanyue-llk wants to merge 1 commit into
Conversation
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.
Result editions need explicit major/minor/patch rules and honest publication dates, independently of the Python package version. Add a shared result-version module, template --kind, release summary/date preflight, numeric tuple allocation and previous-edition identity. Preserve historical vN discovery, fork retries, rebase collisions and exact live-publication checks; allocated date/previous identity do not create duplicate retry branches. Measurements and source provenance remain unchanged.
Coordinates with lexmount/webstone-site#15; depends on #293 and must retarget main after it merges. This does not bump, tag or release the Webstone software package.
Validation: 123 focused result/package/contract tests pass; Ruff passes. Full CI and current-head review are required before merge.