Bump the github-actions group with 3 updates

[dependabot[bot]]

Bumps the github-actions group with 3 updates: github/branch-deploy, actions/setup-node and github/codeql-action.

Updates github/branch-deploy from 9.7.0 to 9.8.1

Release notes

Sourced from github/branch-deploy's releases.

v9.8.1

What's Changed

A follow-up to the v9.8.0 release to implement GraphQL pagination to make "latest deployment checks" more robust when using enforced deployment order.

• Latest Deployments Pagination by @​GrantBirki in github/branch-deploy#307
• node package updates by @​GrantBirki in github/branch-deploy#308

Full Changelog: https://github.com/github/branch-deploy/compare/v9.8.0...v9.8.1

v9.8.0

Enforced Deployment Order 🚀

Introducing a long requested feature, enforced deployment order...

Summary

This pull request does the following:

• adds a new enforced_deployment_order input option that can be used to require deployments to take place "in order" and for each to pass before the next one can be triggered
• adds a new needs_to_be_deployed output that maps to the environments that require successful deployments if a deployment attempt is rejected

Detailed

This feature is one that has been requested by folks internally and externally to GitHub for a long time (over a year). This pull request makes it so that users can now control the order in which deployments are made (if they choose to do so).

This feature is optional and can be enabled by setting, enforced_deployment_order: <env1>,<env2>,<env3>. The value for enforced_deployment_order is a string that is read from left->right with each value separated by commas. Each value in this comma separated list is an environment that you wish to use in an "enforced deployment order". Here is an example:

- uses: github/branch-deploy@vX.X.X
  id: branch-deploy
  with:
    environment_targets: development,staging,production
    enforced_deployment_order: development,staging,production

This means that your project has three environments in total (development,staging,production). The enforced_deployment_order input option specifies that your environments must now be deployed in the order in which they are written. So if you want to deploy to production, you must first have a successful (and active) deployment to development and staging before the branch-deploy Action will allow you to trigger a deployment to production.

---

For more details, please see the pull request that implemented these changes here or the official documentation.

---

What's Changed

• Bump the github-actions group with 2 updates by @​dependabot in github/branch-deploy#301
• Bump @​types/node from 22.5.1 to 22.5.2 in the npm-dependencies group by @​dependabot in github/branch-deploy#302
• Enforced Deployment Order by @​GrantBirki in github/branch-deploy#304

... (truncated)

Commits

• 368e17c Merge pull request #308 from github/node-updates
• 11ee5ec run npm update
• ef4f017 Merge pull request #307 from github/latest-deployments-pagination
• e583b76 sprinkle in some debug statements
• a6d2b24 add pagination logic to latestActiveDeployment() to make it more robust
• d806f9d bundle
• 4788222 rename method for clarity
• 60d5a42 move comment for clarity
• 409f6de Merge pull request #305 from github/node-updates
• 0bc9873 update all node packages with npm update
• Additional commits viewable in compare view

Updates actions/setup-node from 4.0.3 to 4.0.4

Release notes

Sourced from actions/setup-node's releases.

v4.0.4

What's Changed

• Add workflow file for publishing releases to immutable action package by @​Jcambass in actions/setup-node#1125
• Enhance Windows ARM64 Setup and Update micromatch Dependency by @​priyagupta108 in actions/setup-node#1126

Documentation changes:

• Documentation update in the README file by @​suyashgaonkar in actions/setup-node#1106
• Correct invalid 'lts' version string reference by @​fulldecent in actions/setup-node#1124

New Contributors

• @​suyashgaonkar made their first contribution in actions/setup-node#1106
• @​priyagupta108 made their first contribution in actions/setup-node#1126
• @​Jcambass made their first contribution in actions/setup-node#1125
• @​fulldecent made their first contribution in actions/setup-node#1124

Full Changelog: https://github.com/actions/setup-node/compare/v4...v4.0.4

Commits

• 0a44ba7 Correct version string (#1124)
• 97ca147 Merge pull request #1125 from actions/add-is-release-workflow
• aa363de Create publish-immutable-action.yml
• 1c7b2db Fix: windows arm64 setup (#1126)
• 26961cf Documentation update in the README file (#1106)
• See full diff in compare view

Updates github/codeql-action from 3.26.6 to 3.26.10

Changelog

Sourced from github/codeql-action's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

[UNRELEASED]

No user facing changes.

3.26.10 - 30 Sep 2024

• We are rolling out a feature in September/October 2024 that sets up CodeQL using a bundle compressed with Zstandard. Our aim is to improve the performance of setting up CodeQL. #2502

3.26.9 - 24 Sep 2024

No user facing changes.

3.26.8 - 19 Sep 2024

• Update default CodeQL bundle version to 2.19.0. #2483

3.26.7 - 13 Sep 2024

• Update default CodeQL bundle version to 2.18.4. #2471

3.26.6 - 29 Aug 2024

• Update default CodeQL bundle version to 2.18.3. #2449

3.26.5 - 23 Aug 2024

• Fix an issue where the csrutil system call used for telemetry would fail on MacOS ARM machines with System Integrity Protection disabled. #2441

3.26.4 - 21 Aug 2024

• Deprecation: The add-snippets input on the analyze Action is deprecated and will be removed in the first release in August 2025. #2436
• Fix an issue where the disk usage system call used for telemetry would fail on MacOS ARM machines with System Integrity Protection disabled, and then surface a warning. The system call is now disabled for these machines. #2434

3.26.3 - 19 Aug 2024

• Fix an issue where the CodeQL Action could not write diagnostic messages on Windows. This issue did not impact analysis quality. #2430

3.26.2 - 14 Aug 2024

• Update default CodeQL bundle version to 2.18.2. #2417

3.26.1 - 13 Aug 2024

No user facing changes.

... (truncated)

Commits

• e2b3eaf Merge pull request #2507 from github/update-v3.26.10-2617ff2d3
• 7dbbf6d Update changelog for v3.26.10
• 2617ff2 Merge pull request #2502 from github/henrymercer/zstd-experiment
• 46e0c78 Merge pull request #2504 from github/mergeback/v3.26.9-to-main-461ef6c7
• da7be78 Update checked-in dependencies
• ae1c6a2 Update changelog and version after v3.26.9
• 461ef6c Merge pull request #2503 from github/update-v3.26.9-f861efb2b
• 00b1146 Update changelog for v3.26.9
• f861efb Merge pull request #2498 from github/dependabot/npm_and_yarn/npm-9874b37b58
• 6b2f7e7 Run PR checks using JS only
• 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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions

[github-actions[bot]]

👋 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!

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