ci(publish): finalize Sentry release after publishing#450
Merged
Conversation
Add a step to the publish workflow that associates commits, finalizes the release, and creates a production deploy marker in Sentry. Sourcemaps are already uploaded during the CI build — this completes the release lifecycle. Also adds fetch-tags to the checkout so set-commits --auto can find the previous release tag boundary. The step uses continue-on-error since it's post-publish telemetry that must not block issue closure.
BYK
force-pushed
the
ci/finalize-sentry-release
branch
from
13468c6 to
27bb340
Compare
6 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
1 participant
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
Add Sentry release finalization to the publish workflow. Currently, sourcemaps are uploaded during CI builds but the release is never finalized — meaning Sentry doesn't track commits, deploys, or release health for published versions.
Changes
.github/workflows/publish.ymlNew step: "Finalize Sentry release" (after
craft publish, before issue close):sentry-cli releases set-commits --auto— associates commits since the previous release tagsentry-cli releases finalize— marks the release as live with adateReleasedtimestampsentry-cli releases deploys new -e production— creates a deploy marker for release healthAdded
fetch-tags: trueto the checkout step soset-commits --autocan find the previous release tag boundary.Uses
continue-on-error: truesince this is post-publish telemetry — a Sentry API outage must not block the issue from being closed or trigger false "publish failed" comments.What this does NOT change
ci.yml) — sourcemap upload stays where it is.craft.yml— no Craft config changes needed