Branch Deploy Versions Save

Enabling Branch Deployments through IssueOps with GitHub Actions - If you find this project useful, give it a star! ⭐️

v9.3.0

5 days ago

What's Changed

:label: Labels! :label:

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 :rocket:

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.

Full Changelog: https://github.com/github/branch-deploy/compare/v9...v9.3.0

v9.2.0

3 weeks ago

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.

New Contributors

Full Changelog: https://github.com/github/branch-deploy/compare/v9...v9.2.0

v9.1.3

2 months ago

What's Changed

A small bug fix

New Contributors

Full Changelog: https://github.com/github/branch-deploy/compare/v9.1.2...v9.1.3

v9.1.2

2 months ago

What's Changed

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

Full Changelog: https://github.com/github/branch-deploy/compare/v9.1.1...v9.1.2

v9.1.1

3 months ago

What's Changed

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

New Contributors

Full Changelog: https://github.com/github/branch-deploy/compare/v9.1.0...v9.1.1

v9.1.0

4 months ago

Overview

This release introduces a new input option called checks (thanks to @Ugzuzg! 🎉). The checks feature has been a long sought after feature of this Action to give teams better control over what CI checks have to be passing in order for a deployment to proceed. This feature was originally requested way back in 2022 and it has finally landed!

The detailed documentation around the checks input can be found here.

TL;DR: A new input option called checks allows for teams to choose whether they want all CI checks to pass before a deployment can proceed or if only the explicitly required CI checks need to be passing.

What's Changed

New Contributors

Full Changelog: https://github.com/github/branch-deploy/compare/v9...v9.1.0

v9.0.0

5 months ago

What's Changed

⚠️ potentially breaking change! ⚠️

The vast majority of teams should be able to upgrade to v9.0.0 without any issues

It should be noted that this change is only "breaking" in the sense that unexpected behavior may take place for teams using more unique git flows for development. If you want to maintain the current state of this Action on v9.0.0 and beyond, all you need to do is to simply set outdated_mode: "pr_base" in the Action configuration. Most teams using this Action will not notice any issues upgrading to v9.x.x.

This release introduces a new input option (outdated_mode) for fine grain control over deployments when a branch is deemed "out-of-date" 🎉. These changes were introduced in https://github.com/github/branch-deploy/pull/237 and the aforementioned pull request contains a lot of information around these changes. You can also view the detailed documentation around this new input option to learn more and how you and your team can use it. Enjoy!

Full Changelog: https://github.com/github/branch-deploy/compare/v8...v9.0.0

Huge thank you to @jessew-albert for helping out with the features in this release! 🙇

v8.2.1

6 months ago

This patch release contains internal dependency updates

What's Changed

Full Changelog: https://github.com/github/branch-deploy/compare/v8...v8.2.1

v8.2.0

6 months ago

What's Changed

Full Changelog: https://github.com/github/branch-deploy/compare/v8...v8.2.0

v8.1.2

7 months ago

What's Changed

This release updates internal node dependencies that this Action uses

Full Changelog: https://github.com/github/branch-deploy/compare/v8...v8.1.2