Update github/branch-deploy action to v8 - autoclosed

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
github/branch-deploy	action	major	v7.5.2 -> v8.2.1

---

Release Notes

github/branch-deploy (github/branch-deploy)

v8.2.1

Compare Source

This patch release contains internal dependency updates

What's Changed

• Bump the github-actions group with 4 updates by @​dependabot in https://github.com/github/branch-deploy/pull/233
• Bump the npm-dependencies group with 4 updates by @​dependabot in https://github.com/github/branch-deploy/pull/232
• node package updates by @​GrantBirki in https://github.com/github/branch-deploy/pull/234

Full Changelog: github/branch-deploy@v8...v8.2.1

v8.2.0

Compare Source

What's Changed

• Added: Support for GitHub EMU handles @​GrantBirki in https://github.com/github/branch-deploy/pull/227
• Updated: Internal Node Packages by @​GrantBirki in https://github.com/github/branch-deploy/pull/228

Full Changelog: github/branch-deploy@v8...v8.2.0

v8.1.2

Compare Source

What's Changed

This release updates internal node dependencies that this Action uses

• add new tag release workflow for major tags by @​GrantBirki in https://github.com/github/branch-deploy/pull/222
• add dependabot config by @​GrantBirki in https://github.com/github/branch-deploy/pull/223
• Bump the github-actions group with 3 updates by @​dependabot in https://github.com/github/branch-deploy/pull/224
• Bump the npm-dependencies group with 7 updates by @​dependabot in https://github.com/github/branch-deploy/pull/225

Full Changelog: github/branch-deploy@v8...v8.1.2

v8.1.1

Compare Source

This patch release simply upgrades internal node packages and dependencies

What's Changed

• Update Examples Documentation by @​GrantBirki in https://github.com/github/branch-deploy/pull/220
• Node Updates by @​GrantBirki in https://github.com/github/branch-deploy/pull/221

Full Changelog: github/branch-deploy@v8.1.0...v8.1.1

v8.1.0

Compare 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 history
• disable_naked_commands - Prevent naked deploy commands and enforce environment usage in your commands

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

• allow_sha_deployments
• disable_naked_commands

What's Changed

• sha deployments by @​GrantBirki in https://github.com/github/branch-deploy/pull/212
• Prevent Naked Deploys by @​GrantBirki in https://github.com/github/branch-deploy/pull/214
• Update Action Workflows by @​GrantBirki in https://github.com/github/branch-deploy/pull/215
• Dependencies by @​GrantBirki in https://github.com/github/branch-deploy/pull/216
• Output msg fixes by @​GrantBirki in https://github.com/github/branch-deploy/pull/217

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.0

Compare Source

⚠️ Breaking Change ⚠️

TL;DR: If you are using the production_environment input, add a letter s to the end of it to make it plural 😉

This breaking change only effects users who have production_environment defined 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:

...
  uses: github/[email protected]
  with:
    trigger: ".deploy"
    environment: "production"
    stable_branch: "main"
-   production_environment: "production"
+   production_environments: "production"

Release Details

This release enables support for multiple production environments. Before this change, the production_environment input 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_environment input option only takes one value, we cannot set the production-eu environment as "production" via our API call to GitHub (happens inside of this Action for you). However, production-eu is absolutely a production environment, the name even says so!

To solve this, the production_environment input 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:

- name: branch-deploy
  id: branch-deploy
  uses: github/[email protected]
  with:
    trigger: ".deploy"
    noop_trigger: ".noop"
    reaction: "eyes"
    environment: "production"
    stable_branch: "main"
    production_environments: "production,production-eu,production-ap" # <-- a comma separated list of environments

What's Changed

• Support Multiple Production Environments by @​GrantBirki in https://github.com/github/branch-deploy/pull/209

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud