Dashboard › publish › Distillation
410a0528-f95f-490d-96ad-b20757b7e7c9["lore_tm_v1_Z8Wopu08mdMehWIwgc7KlxcOQJ6hpIZ4WxdJxnIlaWs","lore_tm_v1_BvpcUnajjs02h0P3HjfcNZa39Hb20Djfb8QKkMMUy6Q","lore_tm_v1_Utg2JJXq6SKFrmOqjByvck01hFDqIMYfPIGwJ-Wrvoo","lore_tm_v1_tBdcK-LrUbHkgTmpXd7ieh1q6x0va3gyTYGYSSQIgTA","lore_tm_v1_2D4ohvdZ9tYlFYCFX6iXSXRJ8ktZ63RulDn6TwdZNYc","lore_tm_v1__UORKjnkw7myxgeuVer52g_FAWwQ33nIG9nAHWcALdw","lore_tm_v1_jGNmYguT_u2hlSuW04HmTaoMlR_sHwBu5SwCFXLLN84","lore_tm_v1_9ifFnEC5GX9fObGQ129Agp5icNmeD9VZzqrslU4H5B0","lore_tm_v1_qsu6D4YtMeOAJtBYOexmOVNvwhaViLMa0J3J3TWsz6U"]
continue inside the per-issue subshell prints continue: only meaningful in a \for', `while', or `until' loopbut is ignored; execution continued throughafter-x, outer-x, and completed`.src/modules/__tests__/ci-poller-workflow.js to exercise the full CI-success path, all six approval-rejection exits, fail-closed resolver handling, and the required stale-ci-ready remove/revalidate/re-add sequence.yarn vitest run src/modules/__tests__/ci-poller-workflow.js --printConsoleTrace ran 14 tests in src/modules/__tests__/ci-poller-workflow.js: 1 passed and 13 failed in 3049ms.revokes approval when the poller resolver fails; 2. revokes approval when the rewrite response has no body; 3. revokes approval when the rewrite response body is empty; 4. revokes approval when the rewrite response is malformed JSON; 5. revokes approval when the rewrite response is a non-object JSON value; 6. stops the poll cycle when the accepted event cannot be read; 7. stops the poll cycle when initial approval validation fails; 8. stops the poll cycle when post-CI approval validation fails; 9. stops the poll cycle when CI-ready proof recording fails; 10. stops the poll cycle when CI-ready proof output is malformed; 11. stops the poll cycle when the CI-ready proof comment fails; 12. stops the poll cycle when final approval validation fails; 13. removes stale ci-ready before revalidating and adding it.issue edit 1 -R getsentry/publish --remove-label ... to revoke approval, invalid continue statements at shell lines 65, 85, 215, and 250 did not terminate the poll cycle, and the workflow lacked issue edit 1 -R getsentry/publish --remove-label ci-ready.${{ github.token }} at shell line 254, producing bad substitution; assistant identified this as a test-harness artifact because GitHub Actions normally interpolates the expression before Bash execution, not as production workflow behavior.src/publish/post-result.js; its 11-line implementation imports processEndState from ../modules/process-end-state, getGitHubToken from ../libs/github, and @actions/github; creates context and octokit; parses process.env.PUBLISH_ARGS; reads status from process.argv.slice(2)[0]; and invokes processEndState({ context, octokit, inputs, status }).src/modules/__tests__/ci-poller-workflow.js to substitute the raw ${{ github.token }} Actions expression in the test harness before rerunning regressions, ensuring subsequent failures measure workflow behavior rather than Bash interpolation artifacts.