Dashboard › publish › Distillation
db09411f-c4fb-47df-be28-c987cd7dd8de["lore_tm_v1_gHF9ggOxbChbA1YnjcFYkqH7IWWcGeJPHxnQDjEnS0I","lore_tm_v1_l6Ns95doM0x3L8hk4UcrOvAoyzJq4IN86oDhfj3OqNM","lore_tm_v1_2p7bBqTlTAGrD67wzVVsytlXuXvhYsx9E6bprV_e7Cs","lore_tm_v1_4x2mMm7fDXTkUqQq0dOvDRHh4RyFJhOmL_YfXZOfd7k","lore_tm_v1_bQosap56s_5L9T3Srdb_ZPX-1YNBhZbx26coTPDbqNg","lore_tm_v1_5EFUzQOzath6d1TUsgOkVFhBapLmR6XzYFQCsjz9L34","lore_tm_v1_s6O4JlqtYzBm5Bjx9ac8w819B6HqaNqHJeFxVbxS2S0"]
accepted-label removal fails immediately, and 2. the informational publication-start step must be best-effort rather than a publication gate.src/publish/update-issue.js showed main() obtains github.context and an Octokit client via github.getOctokit(getGitHubToken()); optionally parses PUBLISH_ARGS, warning Could not parse publish inputs; skipping target update on invalid JSON; then calls await updateIssue({ context, octokit, inputs }). Top-level errors are logged and set process.exitCode = 1.src/modules/__tests__/update-issue.js and src/publish/__tests__/publish-workflow.js. The cleanup regression requires a duplicate removeLabel 404 to be treated as already clean while delayed target restoration completes; the workflow regression requires Inform start to include continue-on-error: true.yarn vitest run src/modules/__tests__/update-issue.js src/publish/__tests__/publish-workflow.js --printConsoleTrace using Yarn v1.22.22 and Vitest v4.1.0; result was 2 failed test files, 2 failed tests, and 13 passed tests out of 15, duration 346ms, exit code 1.src/modules/__tests__/update-issue.js had 1 failure among 8 tests: restores targets when accepted was already removed failed at line 192 because updateIssue({ context: updateTargetsArgs.context, octokit }) rejected with Error: Not Found { status: 404 } instead of resolving to undefined. The mocked 404 originated at line 184, confirming duplicate label removal currently prevents successful cleanup completion.src/publish/__tests__/publish-workflow.js had 1 failure among 7 tests: does not make the informational start comment a publication gate failed at line 32 because the Inform start workflow section lacked continue-on-error: true.Inform start step uses if: steps.inputs.outcome == 'success' && steps.release-revision.outcome == 'success', sets GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}, and runs node .__publish__/src/publish/post-workflow-details.js; its missing continue-on-error: true means failure of this informational step can gate publication.