You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Align own-release tag admission and verification grammars #6378
The new composite publisher accepts semantic-version tags with build metadata, but the platform's own-release signer grammar rejects that suffix. An admitted release can therefore have a signing identity the consumer does not accept.
Compare the own-release subject grammar in the current Tenant graph. It ends after the optional prerelease and does not accept a build suffix.
Compare the template's matching compatibility grammar at PR #300 head.
Expected Behavior
Every admitted release identity is accepted by the intended verification layers, or admission rejects unsupported release forms before publication.
Actual Behavior
The producer and consumer grammars differ. This is source-level evidence, not an induced publication or production failure. Reported finding.
Acceptance Criteria
Align the admitted tag grammar and all own-release verification layers through a reviewed producer or consumer change.
Use real admission and verification entrypoints to cover ordinary, prerelease and build-metadata tags, including malformed and cross-repository negative cases.
Preserve immutable tags, exact repository binding, finding/security gates and compatibility with valid existing releases.
Revalidate the template's compatibility reader and record publication/readback evidence separately from source merge.
Audience: release authors and operators of own-signed tenants. Size: Small to Medium depending on the chosen admission or verification change. Related: #6306 and platform-tenant-template#300. Part of devantler-tech/monorepo#5046. New intake is Backlog.
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Producer side aligned and published..github#949 merged at 02:23Z and shipped in v21.7.1 (tag commit 684b50681e3bd1fc6f3f48ad4c473073a051f5f1). The publisher now refuses a release tag carrying +BUILD metadata, so an admitted tag always fits the platform's own-release subject grammar, which has no build suffix. That grammar is unchanged.
Checked against that head: the admission entrypoint refuses v1.2.3+abc with an instruction to drop the suffix, and admits v1.2.3 and v1.2.3-rc.1 past the tag check. The action's own test covers the malformed and cross-repository cases.
Still open here: revalidating the template's compatibility reader and recording publication evidence. Both depend on platform-tenant-template#300 adopting v21.7.1, and that PR also waits on #6377 and template#301.
Closing: the producer side is aligned. The composite publish action refuses build metadata on release tags since v21.7.2 (actions/publish-app/admit.sh lines 52-64: a tag carrying + fails admission before anything is signed), so every admitted release identity is one the platform grammar accepts. Decision recorded in ADR 0019 (devantler-tech/monorepo#5095, epic devantler-tech/monorepo#5094).
Activity
coderabbitai commentedon Nov 15, 2026
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
chore: agent-claim #6378 nonce=846582a759e542e2f4c56a3da4290683
fix(publish-app): refuse release tags with build metadata (#949)
devantler commentedon Nov 16, 2026
Producer side aligned and published. .github#949 merged at 02:23Z and shipped in v21.7.1 (tag commit
684b50681e3bd1fc6f3f48ad4c473073a051f5f1). The publisher now refuses a release tag carrying+BUILDmetadata, so an admitted tag always fits the platform's own-release subject grammar, which has no build suffix. That grammar is unchanged.Checked against that head: the admission entrypoint refuses
v1.2.3+abcwith an instruction to drop the suffix, and admitsv1.2.3andv1.2.3-rc.1past the tag check. The action's own test covers the malformed and cross-repository cases.Still open here: revalidating the template's compatibility reader and recording publication evidence. Both depend on platform-tenant-template#300 adopting v21.7.1, and that PR also waits on #6377 and template#301.
devantler commentedon Nov 16, 2026
Closing: the producer side is aligned. The composite publish action refuses build metadata on release tags since v21.7.2 (
actions/publish-app/admit.shlines 52-64: a tag carrying+fails admission before anything is signed), so every admitted release identity is one the platform grammar accepts. Decision recorded in ADR 0019 (devantler-tech/monorepo#5095, epic devantler-tech/monorepo#5094).🤖 Generated with Claude Code