Skip to content

feat(results): allocate semantic editions and release dates - #294

Open
lanyue-llk wants to merge 1 commit into
feat/reviewed-result-submissionsfrom
feat/semantic-result-versions
Open

lanyue-llk wants to merge 1 commit into
feat/reviewed-result-submissionsfrom
feat/semantic-result-versions

Conversation

@lanyue-llk

Copy link
Copy Markdown
Contributor

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.

flowchart TD
  A[Public measurements] --> B[CLI preflight and edition allocation]
  B --> C[Personal fork and result PR]
  C --> D[Trusted website checks and approval]
  D --> E[Immutable edition and deployment]
Loading

Validation: 123 focused result/package/contract tests pass; Ruff passes. Full CI and current-head review are required before merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant