Skip to content

Clarify release version policy - #74

Merged
ip332 merged 1 commit into
mainfrom
release/version-policy
Sep 18, 2026
Merged

ip332 merged 1 commit into
mainfrom
release/version-policy

Conversation

@ip332

@ip332 ip332 commented Sep 18, 2026

Copy link
Copy Markdown
Owner

Summary

  • clarify that normal Git checkouts use commit-count-derived development versions;
  • document that release tags provide the numeric version for archive fallback metadata and packaged artifacts;
  • retain numeric X.Y.Z package versions for -rc.N tags;
  • make the release reconstruction check explicit about the tag-derived artifact invariant.

The previous documentation incorrectly implied that a development checkout's numeric version must equal the release tag's numeric version. This correction matches the established v0.1.30-rc.2 release behavior.

Validation

  • Release artifact manifest tests: 5/5
  • git diff --check: PASS

No production code or normal Git version resolver changes. No compatibility epoch or format changes. No RC3 notes or artifacts are included.

@ip332
ip332 merged commit 1530cb4 into main Sep 18, 2026
6 checks passed
@ip332
ip332 deleted the release/version-policy branch September 18, 2026 23:52
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