Enabling Branch Deployments through IssueOps with GitHub Actions - If you find this project useful, give it a star! ⭐️
A small bug fix
Full Changelog: https://github.com/github/branch-deploy/compare/v9.1.2...v9.1.3
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
This release contains one bug fix, some documentation updates, and dependency updates
Full Changelog: https://github.com/github/branch-deploy/compare/v9.1.0...v9.1.1
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.
Full Changelog: https://github.com/github/branch-deploy/compare/v9...v9.1.0
⚠️ potentially breaking change! ⚠️
The vast majority of teams should be able to upgrade to
v9.0.0without 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! 🙇
This patch release contains internal dependency updates
Full Changelog: https://github.com/github/branch-deploy/compare/v8...v8.2.1
Full Changelog: https://github.com/github/branch-deploy/compare/v8...v8.2.0
This release updates internal node dependencies that this Action uses
Full Changelog: https://github.com/github/branch-deploy/compare/v8...v8.1.2
This patch release simply upgrades internal node packages and dependencies
Full Changelog: https://github.com/github/branch-deploy/compare/v8.1.0...v8.1.1
This release introduces two new input options!
allow_sha_deployments - Enable deployments to exact SHA1 or SHA256 hashes that represent a point-in-time in your commit historydisable_naked_commands - Prevent naked deploy commands and enforce environment usage in your commandsThese new input options can be enabled like so:
- uses: github/[email protected]
id: branch-deploy
with:
allow_sha_deployments: "true" # <-- allow deployments to SHA hashes
disable_naked_commands: "true" # <-- prevent the use of .deploy without a specific <environment>
Both of these new input options are disabled by default but can be enabled if you choose to do so. Please ensure you read the documentation about each option before toggling them on as they can drastically change the behavior of this Action
Documentation:
Thanks to @tiagonbotelho for the SHA deployment suggestion and @mnaser for UX suggestions with disabling "naked commands"
Full Changelog: https://github.com/github/branch-deploy/compare/v8.0.0...v8.1.0