Releases: github/branch-deploy
v4.3.0
v4.3.0
Adds the .help
command to the Action 🎉
The help command uses your Action's configuration to generate a dynamic help command output directly on your pull request so contributors know how to operate deployments through IssueOps.
What's Changed
- Help Command by @GrantBirki in #98
Full Changelog: v4.2.1...v4.3.0
v4.2.1
v4.2.1
What's Changed
- Blocked Merge State - Bug by @GrantBirki in #97
Full Changelog: v4.2.0...v4.2.1
v4.2.0
v4.2.0
What's Changed
- Environment Bypasses for Checks and Reviews by @GrantBirki in #96
Full Changelog: v4.1.0...v4.2.0
v4.1.0
v4.1.0
What's Changed
- Merge commit comparison by @GrantBirki in #84
- use compareCommitsWithBasehead and rest. by @GrantBirki in #85
- Change post by @GrantBirki in #86
- Payload type by @GrantBirki in #87
- Create deploy fix by @GrantBirki in #88
- improve logs and potential sorting fix by @GrantBirki in #89
- Merge commit sha fixes by @GrantBirki in #90
Full Changelog: v4.0.0...v4.1.0
v4.0.0
What's Changed
- Clarify alternate commands in README by @garnertb in #80
- Deployment Bug by @GrantBirki in #82
- Production Environment Feature by @GrantBirki in #83
📢 All users should upgrade to this release (v4.0.0) if possible as it fixes a critical bug where the deployment environment does not correctly get set when creating a new deployment. Many users who just use production
were not impacted by this issue but all users who were using a unique production name (example: prod or prd) were impacted. This release contains fixes for this issue! 🎉 Huge thanks to @mwatson-x for discovering this bug in #81
This release also introduces a new optional input for the Action in #83 which allows users to specify a production_environment
if the name is unique rather than just plain old production (examples: prod, prd, main, etc)
New Contributors
Full Changelog: v3.1.0...v4.0.0
v3.1.0
v3.1.0
The main changes of this release are:
- Fixes a bug where no status checks is set to
success
rather thannull
- Adds a new GitHub Actions output that contains the
deployment_id
of the the deployment created by this Action
What's Changed
- add related lock Action notes by @GrantBirki in #69
- Clarify permissions in README by @tiagonbotelho in #75
- update documentation around permissions by @GrantBirki in #77
- fixing bug with no check statuses - should be set to null by @GrantBirki in #78
- Tiagonbotelho/expose deployment id output by @GrantBirki in #79
New Contributors
- @tiagonbotelho made their first contribution in #75
Full Changelog: v3.0.3...v3.1.0
v3.0.3
v3.0.3
This release updates the @actions/core
library due to the deprecation of a few core methods
What's Changed
- Update Actions Core by @GrantBirki in #65
Full Changelog: v3.0.2...v3.0.3
v3.0.2
v3.0.2
Bump ncc
dependency version to the latest available
What's Changed
- Rollback Docs by @GrantBirki in #61
- bump ncc by @GrantBirki in #63
Full Changelog: v3.0.1...v3.0.2
v3.0.1
v3.0.1
A patch release to support an improved CI job
What's Changed
- add package-check by @GrantBirki in #59
Full Changelog: v3.0.0...v3.0.1
v3.0.0
v3.0.0
This release is a new major release as it changes the structure of the messages which the branch-deploy Action presents. This is a major change as it may break workflows that rely on the structure of these comments.
The majority of users should be able to use this version without any issues. Enjoy!
Examples 📸
Full Changelog: v2.4.1...v3.0.0