Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36502
62f9cb7a fix(repo): move fallback text into attachment to stop duplicate Slack message line Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FFLmji2EynJs1nSK1Q8i2W
by Claude
Succeeded
36502
62f9cb7a fix(repo): move fallback text into attachment to stop duplicate Slack message line Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FFLmji2EynJs1nSK1Q8i2W
by Claude
Failed
36502
553ff307 fix(repo): restore title, colored border, and footer styling for Slack publish notifications Wraps each publish notification's Block Kit `blocks` array inside a top-level `attachments` entry with a `color` field, which is Slack's supported way to combine a legacy-attachment colored left border with full Block Kit layout. Also adds a `header` block as the first block in each message to restore the bold title line that the old ravsamhq/notify-slack-action `notification_title` used to render. - report-pending-publish: title branches on PR vs non-PR exactly like the existing MAIN_TEXT branching ("PR #<n> Publish Pending Review" / "Publish Pending Review"), matching the old notification_title text. Color "good" - the literal value ravsamhq/notify-slack-action's actionColor() returned for a "success" job status (confirmed from its dist/index.js at the pinned SHA used previously in this repo). - publish (approved step): title "Publish Approved", color "good", no footer block (short single-purpose message). - report-published: title "Published Successfully", color "good", keeps the existing context block with the run link. All existing env vars, mention logic, and PR/non-PR branching are unchanged - only the jq payload construction is restructured.
by Claude
Succeeded
36502
50b629bc fix(repo): use Slack Block Kit for cleaner publish notification formatting Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FFLmji2EynJs1nSK1Q8i2W
by Claude
Succeeded
36502
1029635f fix(repo): surface real Slack API errors instead of silently swallowing them Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FFLmji2EynJs1nSK1Q8i2W
by Claude
Succeeded
36502
09440670 fix(repo): use compact jq output for Slack payload steps to avoid multiline GITHUB_OUTPUT error jq -n pretty-prints by default, and the payload was written to $GITHUB_OUTPUT via a plain `echo "payload=$PAYLOAD" >> "$GITHUB_OUTPUT"`, which only supports single-line values. This caused the "Report Pending Publish to Slack" job to fail with "Unable to process file command 'output' successfully" on run https://github.com/nrwl/nx/actions/runs/30463674593. Add -c to both jq -n invocations (report-pending-publish and report-published) so the JSON payload is always emitted on a single line.
by Claude
Succeeded
36502
3109fd29 feat(publish): avoid pinging triggering actor, add threaded Slack status updates Replaces the incoming-webhook based Slack notification in report-pending-publish with slackapi/slack-github-action using chat.postMessage and a bot token, since only a bot token can return a message ts for threading. This enables: - Mentioning Craigory + Jack instead of Jason when Jason himself triggered the run (avoids pinging the trigger, avoids a blanket group-tag/bystander effect). - A threaded reply once the publish job starts (approved). - A new report-published job that posts a threaded reply once the publish succeeds. Requires a new SLACK_BOT_TOKEN repo secret; until it's added, the new Slack steps continue-on-error and no-op without affecting the actual npm publish. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FFLmji2EynJs1nSK1Q8i2W
by Claude
Succeeded
36502
3109fd29 feat(publish): avoid pinging triggering actor, add threaded Slack status updates Replaces the incoming-webhook based Slack notification in report-pending-publish with slackapi/slack-github-action using chat.postMessage and a bot token, since only a bot token can return a message ts for threading. This enables: - Mentioning Craigory + Jack instead of Jason when Jason himself triggered the run (avoids pinging the trigger, avoids a blanket group-tag/bystander effect). - A threaded reply once the publish job starts (approved). - A new report-published job that posts a threaded reply once the publish succeeds. Requires a new SLACK_BOT_TOKEN repo secret; until it's added, the new Slack steps continue-on-error and no-op without affecting the actual npm publish. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FFLmji2EynJs1nSK1Q8i2W
by Claude