Distillation

Date: Aug 27, 2026

• 🔴 (13:32) User stated the CI poller always adds the ci-ready label.
• 🟡 (13:32) publish-workspace-acceptance/src/publish/inputs.js imports @actions/github, @actions/core, and detailsFromContext from ../modules/details-from-context; inputs() calls detailsFromContext({ context: github.context }) and writes its result to the result action output via core.setOutput('result', result), then invokes inputs().
• 🟡 (13:33) Commit 6dae341f9bc1378abde7a9022108caded2d22226, feat: propagate release workspaces, was authored and committed by Burak Yigit Kaya <byk@sentry.io> on Aug 26, 2026 at 14:16:47 UTC. It changed .github/workflows/release.yml, action.yml, src/__tests__/action.test.ts, src/commands/__tests__/publish.test.ts, and src/commands/publish.ts: 263 insertions and 5 deletions. (meaning Aug 26, 2026)
• 🟡 (13:33) Commit 6dae341f9bc1378abde7a9022108caded2d22226 adds optional workspace inputs, described as “Named Craft release workspace to prepare and publish,” to both workflow_dispatch and workflow_call in .github/workflows/release.yml, and to action.yml.
• 🟡 (13:33) In src/commands/publish.ts, Craft detects the legacy cwd state file .craft-publish-${newVersion}.json with existsSync() but never reads it because repository contents can be attacker-influenced through PRs and pre-populate an “already published” set; it warns users to migrate pre-seeded publish state to $XDG_STATE_HOME/craft/, specifically the computed publishStateFile.