chore(deps): bump github/branch-deploy from 4.3.0 to 10.0.2

[dependabot]

Bumps github/branch-deploy from 4.3.0 to 10.0.2.

Release notes

Sourced from github/branch-deploy's releases.

v10.0.2

What's Changed

No major changes with this release, just dependency updates 📦

• Workflow Updates by @​GrantBirki in github/branch-deploy#354
• update all node packages with npm update by @​GrantBirki in github/branch-deploy#355
• bump it a patch version by @​GrantBirki in github/branch-deploy#356

Full Changelog: github/branch-deploy@v10.0.1...v10.0.2

v10.0.1

What's Changed

• Bump actions/upload-artifact from 4.4.3 to 4.5.0 in the github-actions group by @​dependabot in github/branch-deploy#349
• Bump @​types/node from 22.10.1 to 22.10.3 in the npm-dependencies group by @​dependabot in github/branch-deploy#350
• Remove maintain permissions by @​VOVELEE in github/branch-deploy#351 (only read, write, and admin were ever actually valid)
• bump release version to v10.0.1 by @​GrantBirki in github/branch-deploy#353

New Contributors

• @​VOVELEE made their first contribution in github/branch-deploy#351

Full Changelog: github/branch-deploy@v10...v10.0.1

v10.0.0

v10 of the github/branch-deploy Action is focused around safety, security, and usability improvements 🚀

BREAKING

Please note that even though there are breaking changes listed, the vast majority of users should be able to simply upgrade to github/branch-deploy@v10 without any issues

• The checks input option can now be used with a comma separated list of CI checks if you only want certain checks to be considered "blocking" in terms of deployments. Read more here.
• Pull requests in the CHANGES_REQUESTED state are now treated the same as PRs in the REVIEW_REQUIRED state.
• The structure and content of the pre/post deployment messages (that get written to PRs) has changed to contain more rich information. This isn't really a breaking change, but it could be if you are parsing these comments in some way.
• The deployment payload that gets set to the GitHub API will now contain two new attributes: params and parsed_params
• By default, you can no longer .deploy or .noop a pull request fork unless it has approvals - reference. These changes have been made as an extra safety check against potentially untrusted commits
• You will no longer be able to deploy a pull request if the target branch is not the default branch - reference1 reference2

Key Changes

• You should use ${{ steps.branch-deploy.outputs.sha }} everywhere instead of ${{ steps.branch-deploy.outputs.ref }} - documentation
• The structure of the deployment payload that gets sent to the GitHub API has a few new attributes - documentation
• You can now have fine grained control to include or ignore CI checks that can (or can't) block your deployments - documentation
• The message rendering system for pre/post deployment messages has been greatly improved. It now has many more variables for custom deployment messages and the default structures have been updated a bit - PR reference
• A new input option has been added commit_verification: true that enforces commits to be signed/verified before they can be deployed by this Action - PR reference
• A lot of new outputs have been added so subsequent workflow steps have access to even more rich data related to deployments
• Preventing the ability to deploy a pull request that is not targeting the default branch
• Branch ruleset warning checks - If you have a potential security misconfiguration in your branch rulesets, this Action will loudly warn you about it in the deployment logs

... (truncated)

Commits

• ea8c5e0 fix
• 58e46eb Merge pull request #356 from github/version-10.0.2
• 2b4c273 bump it a patch version
• 48ff8f9 Merge pull request #355 from github/node-updates
• 6cd241e update all node packages with npm update
• f1804d4 Merge pull request #354 from github/workflow-updates
• 109818f use environment variables
• c1f8134 set persist-credentials to false for all calls to actions/checkout
• 2d57cf4 Merge pull request #353 from github/v10.0.1-release
• 9f4c4f4 bump release version
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[dependabot]

Looks like github/branch-deploy is no longer a dependency, so this is no longer needed.