fix(pipeline): use fail-on-empty-changeset input for CloudFormation deploy action#1459
Merged
cdklabs-automation merged 1 commit intoApr 22, 2026
Conversation
… deploy action The `aws-actions/aws-cloudformation-github-deploy` action renamed its input from `no-fail-on-empty-changeset` to `fail-on-empty-changeset` and changed the type from a stringified flag to a proper boolean. Emit the new input so the generated workflow keeps working with the latest major version of the action.
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
kaizencc
approved these changes
Apr 22, 2026
cdklabs-automation
deleted the
mrgrain/fix/pipeline/use-boolean-fail-on-empty-changeset
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
aws-actions/aws-cloudformation-github-deployaction was bumped to its latest major version in #1451, but that release also renamed theno-fail-on-empty-changesetinput tofail-on-empty-changesetand switched it from a stringified flag to a proper boolean. The generated workflows still emit the old input name, which the new action version no longer recognises, so deploys that produce an empty changeset fail instead of succeeding silently.Emit
fail-on-empty-changeset: falseto preserve the existing behaviour with the current action version. The snapshot updates reflect the new rendering in generated workflow YAML.Fixes #