Update github/branch-deploy action to v9 #1177
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/github-branch-deploy-9.x
branch
from
46afd0e to
700bb79
Compare
renovate
bot
force-pushed
the
renovate/github-branch-deploy-9.x
branch
from
700bb79 to
4e01e1e
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v7.5.2->v9.0.0Release Notes
github/branch-deploy (github/branch-deploy)
v9.0.0Compare Source
What's Changed
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.0and beyond, all you need to do is to simply setoutdated_mode: "pr_base"in the Action configuration. Most teams using this Action will not notice any issues upgrading tov9.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: github/branch-deploy@v8...v9.0.0
Huge thank you to @jessew-albert for helping out with the features in this release! 🙇
v8.2.1Compare Source
This patch release contains internal dependency updates
What's Changed
Full Changelog: github/branch-deploy@v8...v8.2.1
v8.2.0Compare Source
What's Changed
Full Changelog: github/branch-deploy@v8...v8.2.0
v8.1.2Compare Source
What's Changed
This release updates internal node dependencies that this Action uses
Full Changelog: github/branch-deploy@v8...v8.1.2
v8.1.1Compare Source
This patch release simply upgrades internal node packages and dependencies
What's Changed
Full Changelog: github/branch-deploy@v8.1.0...v8.1.1
v8.1.0Compare Source
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:
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:
allow_sha_deploymentsdisable_naked_commandsWhat's Changed
Thanks to @tiagonbotelho for the SHA deployment suggestion and @mnaser for UX suggestions with disabling "naked commands"
Full Changelog: github/branch-deploy@v8.0.0...v8.1.0
v8.0.0Compare Source
This breaking change only effects users who have
production_environmentdefined as one of their input options. Simply add an "s" to the end of the input option and treat it as a comma separated list of strings. Here is an example:Release Details
This release enables support for multiple production environments. Before this change, the
production_environmentinput value only accepted a single environment. This is not idea for projects that might do something like this:.deploy production- Deploys code to the production environment.deploy production-eu- Deploys code to a specialized European production environment (think, GDPR)Since the
production_environmentinput option only takes one value, we cannot set theproduction-euenvironment as "production" via our API call to GitHub (happens inside of this Action for you). However,production-euis absolutely a production environment, the name even says so!To solve this, the
production_environmentinput option will be removed and replaced with its plural counterpart ->production_environments(note the trailing s).Now you can have lots of production environments, like this:
What's Changed
Thanks to @mnaser for the feedback around this improvement 🙇
Full Changelog: github/branch-deploy@v7.5.2...v8.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.