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
Assign the accepted label to this issue to approve the release.
Targets
npm
gcs
registry
docker[release]
docker[latest]
github
brew
gh-pages
Checked targets will be skipped (either already published or user-requested skip). Uncheck to retry a target.
📋 Changelog
Release notes now order GitHub alerts and exclude unsupported or skipped changes, while Maven and registry diagnostics distinguish real repository differences.
New Features ✨
GitHub alerts now appear as ordered release notes, while unsupported alert placements and skipped or reverted PRs remain excluded.
(changelog) Use GitHub alerts in changelog entries as release notes by @BYK with @sentry-junior in #985
Bug Fixes 🐛
Maven errors now expose repository response details, while registry verification ignores omitted falsey values but still detects genuine differences.
(maven) Include Sonatype's response body in API errors by @0xadam-brown with @sentry-junior in #973
(mcp-registry) Ignore empty values the registry drops when verifying a listing by @sentry-junior in #971
Root cause: Craft's own status check stopped the publish because CI had failed on the revision it was given, d2c2a783 (log). The failed check was Verify / win-x64, which hit EBUSY: resource busy or locked, unlink ...craft.exe in src/__tests__/distribution/setup.test.ts (job). This was a CI gate failure, not an infra problem.
Why it ran on the old revision:accepted and ci-ready were added together at 23:00:11 UTC, so the publish job skipped the CI poller and used the revision in the issue body. By then, release/3.14.0 had already been rebuilt to 229e7c8d (on top of master a5dd1ea2), and its Build & Test run is still in progress.
Targets: nothing has published. npm, gcs, registry, docker[release], docker[latest], github, brew and gh-pages are all still pending.
Current state: the issue has ci-pending but not accepted, because the failed run removed it. The CI poller only acts on issues that have both labels, so nothing will happen on its own.
Not retried: a CI gate failure isn't one of the cases where I retry automatically. Whether and when to re-approve is up to the release owner. For reference, the poller path (approval without a manual ci-ready) checks CI on the current release branch head before it publishes. If Verify / win-x64 fails the same way on 229e7c8d, it looks like a Windows file-lock flake in that smoke test.
Activity
github-actions commentedon Nov 19, 2026
Approved. Checking CI status on the release branch. Publishing will start automatically when CI passes.
getsantry commentedon Nov 19, 2026
CI checks failed for getsentry/craft@3.14.0 (
d2c2a783). Publishing is blocked.Failed checks: Verify / win-x64
View check runs
Re-add the accepted label once CI is fixed to retry.
github-actions commentedon Nov 21, 2026
Publishing: run#44959581402
github-actions commentedon Nov 21, 2026
Failed to publish. (run logs)
Bad branch? Open a PR to the release branch to fix it, then add the
acceptedlabel again. Or delete it with ease and start over.github-actions commentedon Nov 21, 2026
Approved. Checking CI status on the release branch. Publishing will start automatically when CI passes.
sentry-junior commentedon Nov 21, 2026
Root cause: Craft's own status check stopped the publish because CI had failed on the revision it was given,
d2c2a783(log). The failed check wasVerify / win-x64, which hitEBUSY: resource busy or locked, unlink ...craft.exeinsrc/__tests__/distribution/setup.test.ts(job). This was a CI gate failure, not an infra problem.Why it ran on the old revision:
acceptedandci-readywere added together at 23:00:11 UTC, so the publish job skipped the CI poller and used the revision in the issue body. By then,release/3.14.0had already been rebuilt to229e7c8d(on top of mastera5dd1ea2), and its Build & Test run is still in progress.Targets: nothing has published. npm, gcs, registry, docker[release], docker[latest], github, brew and gh-pages are all still pending.
Current state: the issue has
ci-pendingbut notaccepted, because the failed run removed it. The CI poller only acts on issues that have both labels, so nothing will happen on its own.Not retried: a CI gate failure isn't one of the cases where I retry automatically. Whether and when to re-approve is up to the release owner. For reference, the poller path (approval without a manual
ci-ready) checks CI on the current release branch head before it publishes. IfVerify / win-x64fails the same way on229e7c8d, it looks like a Windows file-lock flake in that smoke test.github-actions commentedon Nov 21, 2026
Approved. Checking CI status on the release branch. Publishing will start automatically when CI passes.
getsantry commentedon Nov 21, 2026
CI checks passed for getsentry/craft@3.14.0. Publishing is starting now.
github-actions commentedon Nov 21, 2026
Publishing: run#44964243616
github-actions commentedon Nov 21, 2026
Published successfully: run#44964243616