Bump the github-actions group with 2 updates

[dependabot]

Bumps the github-actions group with 2 updates: github/branch-deploy and cloudflare/wrangler-action.

Updates github/branch-deploy from 8.1.2 to 8.2.0

Release notes

Sourced from github/branch-deploy's releases.

v8.2.0

What's Changed

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

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

Commits

• 8973281 Merge pull request #228 from github/node-updates
• 45c86c9 update all internal node packages
• 9e2d366 Merge pull request #227 from github/handle-github-emu-usernames
• 43bd02c add supporting EMU tests
• 2739f81 use new github emu check
• See full diff in compare view

Updates cloudflare/wrangler-action from 2.0.0 to 3.4.0

Release notes

Sourced from cloudflare/wrangler-action's releases.

v3.4.0

Minor Changes

• #213 d13856dfc92816473ebf47f66e263a2668a97896 Thanks @​GrantBirki! - This change introduces three new GitHub Actions output variables. These variables are as follows:

  • command-output - contains the string results of stdout
  • command-stderr - contains the string results of stderr
  • deployment-url - contains the string results of the URL that was deployed (ex: https://<your_pages_site>.pages.dev)

  These output variables are intended to be used by more advanced workflows that require the output results or deployment url from Wrangler commands in subsequent workflow steps.

Patch Changes

• #216 9aba9c34daabca23a88191a5fe1b81fa721c1f11 Thanks @​Cherry! - Fixes issues with semver comparison, where version parts were treated lexicographically instead of numerically.

  Bulk secret uploading was introduced in wrangler 3.4.0, and this action tries to check if the version used is greater than 3.4.0, and then if so, using the new bulk secret API which is faster. Due to a bug in the semver comparison, 3.19.0 was being considered less than 3.4.0, and then using an older and slower method for uploading secrets.

  Now the semver comparison is fixed, the faster bulk method is used for uploading secrets when available.

v3.3.2

Patch Changes

• #171 76d614f Thanks @​1000hz! - Fixed issues that caused the action to fail if any secret or var values contained shell metacharacters.

• #171 473d9cb Thanks @​1000hz! - Bumped DEFAULT_WRANGLER_VERSION to 3.13.2

v3.3.1

Patch Changes

• #193 a4509d5 Thanks @​1000hz! - Fixed the package manager not being inferred based on lockfile when the packageManager input isn't set.

v3.3.0

Minor Changes

• #188 d9a0a00 Thanks @​simpleauthority! - Added support for Bun as a package manager

v3.2.1

Patch Changes

• #190 528687a Thanks @​1000hz! - Fixed action failure when no packageManager specified and no lockfile is found. The action now falls back to using npm.

v3.2.0

Minor Changes

• #166 7d7b988 Thanks @​nix6839! - Support for package managers other than npm, such as pnpm and yarn.

  fixes #156

v3.1.1

Patch Changes

... (truncated)

Changelog

Sourced from cloudflare/wrangler-action's changelog.

Changelog

3.4.0

Minor Changes

• #213 d13856dfc92816473ebf47f66e263a2668a97896 Thanks @​GrantBirki! - This change introduces three new GitHub Actions output variables. These variables are as follows:

  • command-output - contains the string results of stdout
  • command-stderr - contains the string results of stderr
  • deployment-url - contains the string results of the URL that was deployed (ex: https://<your_pages_site>.pages.dev)

  These output variables are intended to be used by more advanced workflows that require the output results or deployment url from Wrangler commands in subsequent workflow steps.

Patch Changes

• #216 9aba9c34daabca23a88191a5fe1b81fa721c1f11 Thanks @​Cherry! - Fixes issues with semver comparison, where version parts were treated lexicographically instead of numerically.

  Bulk secret uploading was introduced in wrangler 3.4.0, and this action tries to check if the version used is greater than 3.4.0, and then if so, using the new bulk secret API which is faster. Due to a bug in the semver comparison, 3.19.0 was being considered less than 3.4.0, and then using an older and slower method for uploading secrets.

  Now the semver comparison is fixed, the faster bulk method is used for uploading secrets when available.

3.3.2

Patch Changes

• #171 76d614f Thanks @​1000hz! - Fixed issues that caused the action to fail if any secret or var values contained shell metacharacters.

• #171 473d9cb Thanks @​1000hz! - Bumped DEFAULT_WRANGLER_VERSION to 3.13.2

3.3.1

Patch Changes

• #193 a4509d5 Thanks @​1000hz! - Fixed the package manager not being inferred based on lockfile when the packageManager input isn't set.

3.3.0

Minor Changes

• #188 d9a0a00 Thanks @​simpleauthority! - Added support for Bun as a package manager

3.2.1

Patch Changes

• #190 528687a Thanks @​1000hz! - Fixed action failure when no packageManager specified and no lockfile is found. The action now falls back to using npm.

3.2.0

... (truncated)

Commits

• a8be0ea Automatic compilation
• 2de0b3d Merge pull request #218 from cloudflare/changeset-release/main
• f2d9b65 Version Packages
• 0e62aca Merge pull request #213 from GrantBirki/write-results-to-a-file
• bd38570 Apply suggestions from code review
• d13856d add changeset
• f88aee4 Merge branch 'main' into write-results-to-a-file
• a5f361f Update src/index.ts
• 9aba9c3 fix: semver comparison (#216)
• 9dd38ad Update package.json
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 <dependency name> 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 <dependency name> 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 <dependency name> 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 <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[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]

Hold please

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.