Bump github/branch-deploy from 6.0.0 to 7.0.0

[dependabot]

Bumps github/branch-deploy from 6.0.0 to 7.0.0.

Release notes

Sourced from github/branch-deploy's releases.

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?

Here are some suggested readings to learn more about why this change was made if you are curious to learn more:

• discussion issue
• pull request containing changes
• deprecation docs

What's Changed

• noop prefix enhancements by @​GrantBirki in github/branch-deploy#169
• isDeprecated Function Fixes by @​GrantBirki in github/branch-deploy#171
• node package updates by @​GrantBirki in github/branch-deploy#172

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

v6.1.0

This release introduces a new input option from @​szymonpk's suggestion github/branch-deploy#163.

This input option is called draft_permitted_targets and allows for users to designate certain environments that can be deployed to via a pull request in a "draft" state. By default, no environments can be deployed to from draft PRs but this option may be configured if you or your organization has a special use case where you would like to deploy a draft pull request.

More details about this change can be found here -> github/branch-deploy#166

What's Changed

• Draft Permitted Targets by @​GrantBirki in github/branch-deploy#166
• Node Dependencies by @​GrantBirki in github/branch-deploy#167

Full Changelog: github/branch-deploy@v6.0.1...v6.1.0

v6.0.1

Updates internal node dependencies

What's Changed

• update unlock-on-merge docs by @​GrantBirki in github/branch-deploy#162
• node package updates by @​GrantBirki in github/branch-deploy#164

... (truncated)

Commits

• 6f4c52d Merge pull request #172 from github/node-package-updates
• d31d750 npm update
• a771361 Merge pull request #171 from github/isDeprecated-function-fixes
• fd70823 bundle
• 461efd3 update tests
• f86dbe5 switch context and octokit positions
• e598272 Merge pull request #169 from github/noop-prefix-enhancement
• 49a2973 bundle
• 931a358 update docsLink
• 2efc1ff add deprecated document
• 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 our 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 development environment with .deploy to development

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

   If anything goes wrong, rollback with .deploy main

5. 🎉 Merge!

Need help? Type .help as a comment or visit the usage guide for more details

Please note, if you have a more complex change, it is advised to claim a deployment lock with .lock <environment> --reason <reason> to prevent other deployments from happening while you are working on your change.

Once your PR has been merged, you can remove the lock with .unlock <environment>.

[GrantBirki]

.deploy

[GrantBirki]

resolved by #210

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.