Skip to content

fix: inline composite action steps so releases don't edit workflow files - #7

Merged
Krustytoe merged 1 commit into
mainfrom
fix/inline-composite-actions
Oct 15, 2026
Merged

Krustytoe merged 1 commit into
mainfrom
fix/inline-composite-actions

Conversation

@Krustytoe

Copy link
Copy Markdown
Owner

Follow-up to #6. The release-please run after #6 merged failed:

⚠ No entries modified in $.version        (terraform-plan.yml, terraform-apply.yml)
##[error]release-please failed: Error adding to tree

Root cause (my mistake in #6):

  1. Release-please handles .yml paths in extra-files with its YAML updater ($.version), not the generic x-release-please-version updater.
  2. GitHub doesn't let GITHUB_TOKEN commit changes under .github/workflows/, so any release automation that rewrites these files would need a PAT or App token with workflow scope.

Fix: inline the steps from actions/terraform-setup, aws-oidc-auth, and azure-oidc-auth (each a SHA-pinned third-party action) into both reusable workflows. With no self-reference, there's no @main, no tag to bump, and no token problem. The composite actions stay published for direct use, and Dependabot keeps all the SHAs current. extra-files goes back to README.md only. Behavior is unchanged: same action versions, same inputs, tflint --init still runs at the repo root.

Validation: actionlint 1.7.12 clean. After merge, release-please should open the v0.3.0 release PR.

🤖 Generated with Claude Code

release-please failed with "Error adding to tree": GITHUB_TOKEN cannot
commit changes under .github/workflows, and .yml extra-files also get the
YAML ($.version) updater rather than the generic one. Inlining the
SHA-pinned steps removes the self-reference entirely, so there is no
@main and nothing for release automation to bump in workflow files.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Krustytoe
Krustytoe merged commit 10f7ce8 into main Oct 15, 2026
1 check passed
@Krustytoe
Krustytoe deleted the fix/inline-composite-actions branch October 15, 2026 20:36
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