Skip to content

docs: investigation report on develop beta tag recompute bug#5211

Open
avallete wants to merge 2 commits intodevelopfrom
claude/fix-ci-beta-tags-P79I4
Open

docs: investigation report on develop beta tag recompute bug#5211
avallete wants to merge 2 commits intodevelopfrom
claude/fix-ci-beta-tags-P79I4

Conversation

@avallete
Copy link
Copy Markdown
Member

@avallete avallete commented May 7, 2026

Documents the root cause of release.yml's plan job recomputing
2.99.0-beta.1 instead of advancing to beta.2: semantic-release
normalizes a prerelease branch's channel to the branch name, not
the prerelease value, so [null]-channel tags never match.

Documents the root cause of release.yml's plan job recomputing
2.99.0-beta.1 instead of advancing to beta.2: semantic-release
normalizes a prerelease branch's channel to the branch name, not
the prerelease value, so [null]-channel tags never match.
@avallete avallete requested a review from a team as a code owner May 7, 2026 16:22
Adds an explicit "channel": "beta" to the develop branch entry in
apps/cli/package.json so semantic-release's branch normalization no
longer falls back to the branch name ("develop") for channel matching,
and threads the channel through release.yml -> release-shared.yml so
the publish job writes refs/notes/semantic-release-<tag> for every
prerelease tag. Without those notes the develop plan job kept
recomputing 2.99.0-beta.1 every push (see
docs/ci-beta-tags-investigation.md).

A one-time backfill of the channel note for v2.99.0-beta.2 on origin
is required before this takes effect on the next develop push.
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.

3 participants