Skip to content

fix(ci): conventional generated-TF commits and bot-safe session names - #142

Merged
Alexanderamiri merged 2 commits into
mainfrom
fix/expand-commit-message
Oct 23, 2026
Merged

Alexanderamiri merged 2 commits into
mainfrom
fix/expand-commit-message

Conversation

@Alexanderamiri

@Alexanderamiri Alexanderamiri commented Oct 23, 2026 •

Copy link
Copy Markdown
Member

Two CI fixes found while rolling out cupcake.

Why

  1. Generated-Terraform commits break app repos' commit checks. expand pushes [skip ci] Update generated Terraform from app.yaml to app branches, including PR branches. Repos that enforce Conventional Commits then reject any push to a branch containing it; this blocked a follow-up push to frosting#249.
  2. Bot-triggered runs fail at the AWS role step. STS role session names are built from GITHUB_ACTOR. Bot actors contain brackets, which STS rejects. The registry's teams-changed dispatch run failed this way (javabin-platform[bot]-…, run 40029013159), and Renovate-triggered app deploys would fail the same way.

What changed

  1. The message is now chore(terraform): update generated Terraform from app.yaml [skip ci]. [skip ci] anywhere in the message still skips workflows.
  2. Session names go through tr -c 'A-Za-z0-9+=,.@_\n-' '-' in tf-plan, docker-build, ecs-deploy and platform-ci.

Checks

actionlint, plus a manual check of the sanitizer on the failing name: javabin-platform-bot--6bd5143d-40029013159.

🤖 Generated with Claude Code

expand pushed '[skip ci] Update generated Terraform from app.yaml' to app
branches, which fails commit-message checks in app repos (Conventional
Commits), blocking pushes to PR branches that contain it. [skip ci]
anywhere in the message still skips workflows.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@Alexanderamiri
Alexanderamiri requested a review from a team as a code owner October 23, 2026 21:49
The session name is built from GITHUB_ACTOR, and bot actors such as
javabin-platform[bot] or renovate[bot] contain brackets, which STS
rejects: the registry's teams-changed dispatch run failed on it, and
Renovate-triggered app deploys would too.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@Alexanderamiri Alexanderamiri changed the title fix(ci): use a conventional commit message for generated Terraform fix(ci): conventional generated-TF commits and bot-safe session names Oct 23, 2026
@github-actions

Copy link
Copy Markdown

Terraform Plan

✅ No changes — infrastructure is up to date.

Plan output
Acquiring state lock. This may take a few moments...
aws_ssm_parameter.atlassian_org_id: Refreshing state... [id=/javabin/platform/atlassian-org-id]
aws_ssm_parameter.atlassian_api_key: Refreshing state... [id=/javabin/platform/atlassian-api-key]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

@Alexanderamiri
Alexanderamiri merged commit a34db44 into main Oct 23, 2026
4 checks passed
@Alexanderamiri
Alexanderamiri deleted the fix/expand-commit-message branch October 23, 2026 22:08
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.

1 participant