Skip to content

Releases: github/branch-deploy

v9.2.0

10 Jun 23:48
0b9d287
Compare
Choose a tag to compare

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: v9...v9.2.0

v9.1.3

22 Apr 16:44
17d9fd7
Compare
Choose a tag to compare

What's Changed

A small bug fix

New Contributors

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

v9.1.2

04 Apr 18:30
f9e741b
Compare
Choose a tag to compare

What's Changed

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

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

v9.1.1

24 Mar 00:22
4c2569b
Compare
Choose a tag to compare

What's Changed

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

New Contributors

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

v9.1.0

17 Feb 21:58
ad494b2
Compare
Choose a tag to compare

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: v9...v9.1.0

v9.0.0

01 Feb 20:12
0ae2f57
Compare
Choose a tag to compare

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 #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: v8...v9.0.0


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

v8.2.1

03 Jan 20:49
153de21
Compare
Choose a tag to compare

This patch release contains internal dependency updates

What's Changed

Full Changelog: v8...v8.2.1

v8.2.0

18 Dec 19:31
8973281
Compare
Choose a tag to compare

What's Changed

Full Changelog: v8...v8.2.0

v8.1.2

01 Dec 19:42
67cd82f
Compare
Choose a tag to compare

What's Changed

This release updates internal node dependencies that this Action uses

Full Changelog: v8...v8.1.2

v8.1.1

25 Oct 16:52
43004c8
Compare
Choose a tag to compare

This patch release simply upgrades internal node packages and dependencies

What's Changed

Full Changelog: v8.1.0...v8.1.1