Repository navigation
ci(release): date-based quarterly version bumps (YYYY.Q.P) - #16
Merged
Merged
Conversation
The dispatch bump logic did semver (major/minor/patch), which conflicts with the documented date-based quarterly model (YYYY.R). A "major" bump of 2026.3.0 produced 2027.0.0; a "minor" produced 2026.4.0 — inconsistent and confusing. Now: - release_type gains `point` (YYYY.Q.P -> .P+1) and `quarter` (YYYY.Q -> next quarter, rolling the year after Q4: 2026.4.x -> 2027.1.0). The old patch/minor/major labels are kept as aliases (patch=point, minor/major=quarter). - Bump math parses YEAR.QUARTER.PT and handles the Q4->Q1 year rollover and 2-field legacy tags (e.g. 2026.2 -> quarter -> 2026.3.0). Verified with 8 unit cases incl. year rollover, legacy tags, and aliases. RELEASES.md updated; actionlint clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Aligns the release pipeline with the quarterly date-based model (4 majors/year).
Problem
release.yml's dispatch did semver bumps (major/minor/patch), conflicting with the documentedYYYY.Rdate-based model. Amajorbump of2026.3.0gave2027.0.0;minorgave2026.4.0— confusing and wrong for a Kali/Parrot-style date scheme.Change
release_typeoptions:point(2026.3.0→2026.3.1) andquarter(2026.3.x→2026.4.0;2026.4.x→2027.1.0with year rollover).patch/minor/majorkept as aliases (patch=point, minor/major=quarter) so nothing breaks.YEAR.QUARTER.PT, handles Q4→Q1 year rollover, and legacy 2-field tags.Verified
8 unit cases pass, including:
2026.3.0 quarter → 2026.4.02026.4.0 quarter → 2027.1.0(year rollover)2026.2 quarter → 2026.3.0(legacy 2-field tag)actionlint clean; RELEASES.md updated.
Release plan context
Model: 4 quarterly majors (
2026.1–2026.4) +.1/.2point releases + continuous rolling/nightly. Next major2026.4targeted early Nov, bundling this session's work (sub-5GB ISO, 0-FAIL build, dashboard removed, re-keyed APT, honest metapackages).🤖 Generated with Claude Code