Bump github/branch-deploy from 6.0.1 to 7.2.0

[dependabot]

Bumps github/branch-deploy from 6.0.1 to 7.2.0.

Release notes

Sourced from github/branch-deploy's releases.

v7.2.0

This release introduces retries for all Octokit requests. This issue was raised in github/branch-deploy#180 which pointed out that potential latency was causing the Action to fail when it was trying to add a file to a branch that didn't quite exist yet. This release adds significant improvements for resiliency when making requests to the GitHub API through Octokit retries.

Users do not need to do anything when upgrading to this release and retries will be handled for you out of the box.

Enjoy! 🚀

What's Changed

• Octokit Retries by @​GrantBirki in github/branch-deploy#181

---

Full Changelog: github/branch-deploy@v7.1.0...v7.2.0

v7.1.0

This release introduces a new input parameter for this Action:

• deploy_message_path - The path to a markdown file which is used as a template for custom deployment messages

You can read more about this change under the dedicated documentation for custom deployment messages.

This release will give users of this Action even more flexibility to customize what their projects deployment messages look like! All this can now be done in our familiar friend, markdown and it also comes with nunjucks template rendering support 🚀.

What's Changed

• File Based Post Deploy Messages by @​GrantBirki in github/branch-deploy#174
• Code cleanup by @​GrantBirki in github/branch-deploy#175
• node package updates by @​GrantBirki in github/branch-deploy#176
• Documentation Updates by @​GrantBirki in github/branch-deploy#177
• add example screenshot by @​GrantBirki in github/branch-deploy#178

Full Changelog: github/branch-deploy@v7.0.0...v7.1.0

v7.0.0

⚠️ Breaking Changes ⚠️

This new major release changes the way that "noop" style commands work. Starting with this release, the .deploy noop command will no longer work and it will be immediately replaced with .noop instead. The core reasoning for this, is so that .noop can become its own standalone command and no longer be a subset of the .deploy command. This will lead to less mistakes, user error, and higher flexibility when customizing this Action for future projects.

What do I need to do?

For most users, you don't need to do anything at all. Simply use .noop (the default) instead of .deploy noop. In fact, if you upgrade to v7.0.0 (this release) and run .deploy noop, you will be presented with a comment containing details about the command to use instead and a link to the deprecation docs

You can always customize the noop_trigger input option to be something else besides .noop (you could do .plan if you're doing Terraform things for example) but the "noop" trigger will never again be a subset of the primary deploy command.

Why was this change made?

... (truncated)

Commits

• d92479f Merge pull request #181 from github/octokit-retries
• 52097b5 add inline comment
• 546d027 add retry logic to 'createOrUpdateFileContents()'
• 8f0a542 bundle
• 7a4cdeb add the retry plugin to the base octokit client
• 8356933 sorting imports
• 639a959 adding '@​octokit/plugin-retry' package
• b7dee40 Merge pull request #178 from github/custom-comment-screenshot
• 6c527d4 add example screenshot
• d3c3eba Merge pull request #177 from github/documentation-updates
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

👋 Thanks for opening a pull request!

If you are new, please check out the trimmed down summary of the deployment process below:

1. 👀 Observe the CI jobs and tests to ensure they are passing

2. ✔️ Obtain an approval/review on this pull request

3. 🚀 Deploy your pull request to the production environment with .deploy

   If anything goes wrong, rollback with .deploy main

4. 🎉 Merge!

If you have a larger change and want to block deployments, you can run .lock --reason <reason> to lock all other deployments (remove with .unlock)

You can view the branch deploy usage guide for additional information