Skip to content

fix(ci): forward AZTEC_FOUNDATION_CI_SLACK_BOT_TOKEN into build container#23473

Merged
ludamad merged 1 commit into
nextfrom
fix/ci-forward-docs-slack-bot-token
May 21, 2026
Merged

fix(ci): forward AZTEC_FOUNDATION_CI_SLACK_BOT_TOKEN into build container#23473
ludamad merged 1 commit into
nextfrom
fix/ci-forward-docs-slack-bot-token

Conversation

@critesjosh
Copy link
Copy Markdown
Contributor

Summary

PR #23293 switched the docs CI scripts (docs/bootstrap.sh, docs/examples/bootstrap.sh, docs/scripts/check_doc_references.sh, docs/scripts/validate_api_ref_links.sh) from SLACK_BOT_TOKEN to AZTEC_FOUNDATION_CI_SLACK_BOT_TOKEN, and added the new secret to the GitHub Actions runner env in .github/workflows/ci3.yml.

The actual build runs inside a docker container started by ci3/bootstrap_ec2, which has its own explicit -e env-passthrough list. That list was not updated, so inside the container the new variable is empty and the docs Slack scripts log AZTEC_FOUNDATION_CI_SLACK_BOT_TOKEN not set, skipping Slack notification and return without posting. As a result, docs-examples failure pings (and any future #docs-alerts traffic from check_doc_references.sh / validate_api_ref_links.sh) silently stopped after #23293 merged.

This adds the missing -e AZTEC_FOUNDATION_CI_SLACK_BOT_TOKEN=${AZTEC_FOUNDATION_CI_SLACK_BOT_TOKEN:-} line next to the existing SLACK_BOT_TOKEN passthrough in ci3/bootstrap_ec2.

Test plan

  • After merge, watch the next merge-queue run that fails a docs-examples step and confirm a notification appears in #docs-alerts.
  • Alternatively, intentionally break a TypeScript example on a throwaway PR with ci-docs label and verify the alert fires.

…iner

PR #23293 switched the docs CI scripts (docs/bootstrap.sh,
docs/examples/bootstrap.sh, docs/scripts/check_doc_references.sh,
docs/scripts/validate_api_ref_links.sh) from SLACK_BOT_TOKEN to
AZTEC_FOUNDATION_CI_SLACK_BOT_TOKEN and plumbed the new secret into
the GitHub Actions runner env in .github/workflows/ci3.yml.

The actual build runs inside a docker container started by
ci3/bootstrap_ec2, which has its own explicit -e env-passthrough list.
That list was not updated, so inside the container the new variable is
empty and the docs Slack scripts log
"AZTEC_FOUNDATION_CI_SLACK_BOT_TOKEN not set, skipping Slack
notification" and return without posting. Notifications stopped after
#23293 merged.

Add the variable to the docker passthrough so the docs CI scripts can
authenticate against the Aztec Foundation CI bot and post to
#docs-alerts.
@critesjosh critesjosh requested a review from ludamad May 21, 2026 14:27
@critesjosh critesjosh marked this pull request as ready for review May 21, 2026 14:27
@critesjosh critesjosh requested a review from charlielye as a code owner May 21, 2026 14:27
@ludamad ludamad added this pull request to the merge queue May 21, 2026
Merged via the queue into next with commit 6f90118 May 21, 2026
30 checks passed
@ludamad ludamad deleted the fix/ci-forward-docs-slack-bot-token branch May 21, 2026 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants