chore(conventions): switch product-repo tag form to bare SemVer numerals#20
Merged
Merged
Conversation
Align with SemVer 2.0.0 FAQ (https://semver.org/spec/v2.0.0.html#is-v123-a-semantic-version) — the canonical version form has no `v` prefix. Update §2 tag format, §3 CHANGELOG heading style, §4 workflow YAML trigger glob, §7 release procedures (UI + CLI), and §8 failure-mode examples. The `awk` extractor in §4 still accepts both `## [0.1.0]` (canonical) and `## [v0.1.0]` (legacy) heading styles for backwards compatibility. Mirrors blackbrowed-labs/thalura-plugin#5 (already merged) which applied the same change to thalura-plugin's release.yml. The reference implementation at blackbrowed-labs/pipeline-test-fixture should be updated separately if it still uses the v-prefix. Co-Authored-By: Claude <noreply@anthropic.com>
3 tasks
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.
Summary
Aligns
docs/PRODUCT_REPO_CONVENTIONS.mdwith the bare-numeral SemVertag form per the SemVer 2.0.0 FAQ:
Mirrors thalura-plugin#5
(already merged) which applied the same change to
thalura-plugin'srelease.yml.thalura-pluginshipped0.1.0on 2026-05-13; theconventions doc was the only canonical artefact still mandating the
legacy
vX.Y.Zform.What changed
Docs-only — single file,
docs/PRODUCT_REPO_CONVENTIONS.md(+33/-29).X.Y.Zwith SemVer FAQ link'v*'→'[0-9]+.[0-9]+.[0-9]+*')Explicitly preserved
awkextractor body + error message at lines 145–158 — keeps thetwo-form tolerance (
\\[v"tag"\\]) for backwards compatibilitywith legacy
## [v0.1.0]headings.actions/checkout@v6reference — action-version pin, not atag-form example.
Website pipeline impact
None. The release loader is tag-form-agnostic end-to-end —
tagNameflows verbatim from GitHub REST →
src/lib/github-api.ts:120→src/content.config.ts:186→src/pages/produkte/[slug].astro:124(version-chip). No
v-prefix manipulation anywhere insrc/orscripts/. Both0.1.0andv0.1.0round-trip identically.Verification
Test plan
dev+ rollout tomain:pipeline-test-fixturewill be updated in the GitHub UI to mirror this convention as
the live end-to-end integration test (Lars-driven).
🤖 Generated with Claude Code