v9.7.0

What's Changed

• Lock Branch Validation by @GrantBirki in #299
• update internal node deps by @GrantBirki in #300

Full Changelog: v9...v9.7.0

v9.6.0

What's Changed

This release mainly contains one minor change to how a few Action inputs used. Some basic input validation is now applied to them, so if you provide an unexpected Action input, the workflow will now fail and log the correct options for the input for you to use instead.

• Input Validation by @GrantBirki in #293
• Improve .help command by @GrantBirki in #294
• Node Updates by @GrantBirki in #295

Full Changelog: v9...v9.6.0

v9.5.0

What's Changed

• Bump actions/upload-artifact from 4.3.3 to 4.3.4 in the github-actions group by @dependabot in #285
• Additional Commit SHA Outputs 🔢 by @GrantBirki in #289
• update all node packages by @GrantBirki in #290
• clean up node dependencies by @GrantBirki in #291

Full Changelog: v9...v9.5.0

v9.4.0

What's Changed

• Allow Post Run Labels to be Conditionally Skipped by @GrantBirki in #277
• node deps and package cleanup by @GrantBirki in #278
• Label Improvements by @GrantBirki in #280
• Test Improvements 🧪 by @GrantBirki in #281

Full Changelog: v9...v9.4.0

v9.3.1

What's Changed

This release includes a minor bug fix in the way that deployment SHAs treat the auto_merge function on deployments. It also includes better test coverage of existing code and some control flow improvements as well.

• Test Fixes / Improvements by @GrantBirki in #275

Full Changelog: v9...v9.3.1

v9.3.0

What's Changed

🏷️ Labels! 🏷️

This release introduces a new feature known as "post deployment labels". These labels can be configured via a set of four new Action inputs:

Input	Required?	Default	Description
successful_deploy_labels	false	""	A comma separated list of labels to add to the pull request when a deployment is successful. Example: "deployed,success"
successful_noop_labels	false	""	A comma separated list of labels to add to the pull request when a noop deployment is successful. Example: "noop,success"
failed_deploy_labels	false	""	A comma separated list of labels to add to the pull request when a deployment fails. Example: "failed,deploy-failed"
failed_noop_labels	false	""	A comma separated list of labels to add to the pull request when a noop deployment fails. Example: "failed,noop-failed"

If you use all (or even some) of these new input options, label will be automatically applied (or removed) from your pull request depending on the resulting state of the deployment.

Here is an example scenario:

1. Someone runs .noop to start a Terraform plan
2. The .noop completes successfully so the branch-deploy Action adds the ready-for-review label on your pull request
3. Your team reviews the PR and approves it
4. Now you are clear to .deploy 🚀

New Outputs!

This Action now exports additional outputs that can be utilized by subsequent workflow steps:

• review_decision
• is_outdated
• merge_state_status
• commit_status
• approved_reviews_count

View the action.yml file in this repo or the main README to learn more about these new outputs

A New Custom Deployment Message Variable!

This release also introduces a new deployment message variable that can be rendered into custom deployment messages:

• approved_reviews_count

This variable will display the number of approved reviews on the pull request at the time of deployment.

---

• Post Deploy Feature Improvements by @GrantBirki in #272
• node package updates by @GrantBirki in #273

---

Full Changelog: v9...v9.3.0

v9.2.0

What's Changed

This release contains a new minor change related to the size of comments that can be posted on PRs. If the comment body (from a deployment) is too large, it will be truncated and collapsed inside of an expandable details block in markdown. This prevents the Action from failing if a comment is over the fixed size limit for GitHub issue comments.

This release also contains internal node package updates for npm packages that this Action relies on.

• Bump the github-actions group with 2 updates by @dependabot in #259
• handle messages that are bigger than issue body limit by @nodeselector in #266
• Bump GrantBirki/json-yaml-validate from 2.7.1 to 3.0.0 in the github-actions group by @dependabot in #264
• update all internal node packages by @GrantBirki in #268
• Truncate improvements by @GrantBirki in #270

New Contributors

• @nodeselector made their first contribution in #266

Full Changelog: v9...v9.2.0

v9.1.3

What's Changed

A small bug fix

• Fixes unchecked sticky by @reggi in #257

New Contributors

• @reggi made their first contribution in #257

Full Changelog: v9.1.2...v9.1.3

v9.1.2

What's Changed

This release updates internal node dependencies that are required for this Action to be packaged and developed

• Bump the npm-dependencies group with 1 update by @dependabot in #252
• Node and Actions updates by @GrantBirki in #254

Full Changelog: v9.1.1...v9.1.2

v9.1.1

What's Changed

This release contains one bug fix, some documentation updates, and dependency updates

• Bump the github-actions group with 3 updates by @dependabot in #245
• Add read access to statuses to required permissions by @greysteil in #248
• Bug: Running unlock when no-lock exists returns an error by @GrantBirki in #250
• Bump the npm-dependencies group with 6 updates by @dependabot in #251

New Contributors

• @greysteil made their first contribution in #248

Full Changelog: v9.1.0...v9.1.1