Skip to content

feat: auto-maintain floating major version tag#5

Closed
TheMeinerLP wants to merge 1 commit into
mainfrom
feat/floating-major-tag
Closed

feat: auto-maintain floating major version tag#5
TheMeinerLP wants to merge 1 commit into
mainfrom
feat/floating-major-tag

Conversation

@TheMeinerLP
Copy link
Copy Markdown
Contributor

@TheMeinerLP TheMeinerLP commented May 11, 2026

Closed — Floating-Major-Tag-Automation nicht gewünscht. Konsumenten pinnen direkt auf @v2.0.0 (siehe Butterfly PR #81, Aonyx-bom PR #39); Renovate handhabt zukünftige Patch-/Minor-Bumps.

Add a workflow that updates `vN` to point at the latest `vN.x.y` tag
whenever a GitHub release is published, so consumers can pin to a major
(`@v2`) and receive non-breaking updates automatically.

A workflow_dispatch trigger with a tag input lets us bootstrap or fix
the floating tag manually (e.g. point `v2` at the existing `v2.0.0`).
@TheMeinerLP TheMeinerLP deleted the feat/floating-major-tag branch May 11, 2026 14:48
TheMeinerLP added a commit that referenced this pull request May 11, 2026
The floating @v2 tag was never auto-maintained (see PR #5), so README
examples that used @v2 pointed to a tag that does not exist. Replace
every @v2 with the current latest concrete tag (@v2.0.1) and clarify in
the Versioning section that consumers must pin to a full vX.Y.Z and rely
on Renovate for bumps. Also document the matrix artifact isolation
behaviour shipped in v2.0.1 and remind contributors that PR titles must
be conventional (otherwise squash merges skip release-please).
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