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