Distillation

Date: Sep 8, 2026

• 🔴 (10:10) User stated that the CI poller always adds ci-ready.
• 🟡 (10:10) Current .github/workflows/publish.yml excerpt indicates the publish workflow uses issue titles formatted like publish: getsentry/foo@1.2.3 to distinguish duplicate publish requests.
• 🟡 (10:10) Current .github/workflows/publish.yml:175 comment states the poller always adds ci-ready, in the context of avoiding a race with waiting-for-ci on the same event.
• 🟡 (10:10) Current .github/workflows/publish.yml excerpt includes an authorization step (id: authorization), GitHub App token creation via actions/create-github-app-token@v3, invalid-approval rejection, ci-pending labeling, poller-token acquisition, and CI-poller triggering.
• 🟡 (10:10) Current .github/workflows/publish.yml excerpt includes a Publish a new version job that requires an issue title beginning publish: and an accepted label.
• 🟡 (10:10) Current .github/workflows/publish.yml excerpt checks out repository contents, parses publish inputs, conditionally handles sentry-javascript with merge target v8, obtains a release-bot token using vars.SENTRY_RELEASE_BOT_CLIENT_ID, and uses __repo__ as a checkout path.
• 🟡 (10:10) Current .github/workflows/publish.yml excerpt writes Craft state to its safe expected location, computes a hash based on the Craft container working directory, and maps publish paths under /github/workspace/__repo__/${CRAFT_PUBLISH_PATH}.
• 🟡 (10:10) Current .github/workflows/publish.yml excerpt uses separate tokens for GHCR.IO and GitHub API access; includes secrets/configuration COCOAPODS_TRUNK_TOKEN, TWINE_VERBOSE: "1", and OSSRH_USERNAME.
• 🟡 (10:10) Current .github/workflows/publish.yml excerpt runs failure handling when ${{ cancelled() || failure() }} and invokes node .__publish__/src/publish/post-result.js failure.