Bump cloudflare/wrangler-action from 3.4.1 to 3.6.1 in the github-actions group

[dependabot]

Bumps the github-actions group with 1 update: cloudflare/wrangler-action.

Updates cloudflare/wrangler-action from 3.4.1 to 3.6.1

Release notes

Sourced from cloudflare/wrangler-action's releases.

v3.6.1

Patch Changes

• #265 2d275a8f2d279dc91912c1ff8023af109ef3280c Thanks @​Maximo-Guk! - Reverts #235 which may have caused the latest version of wrangler to be installed, if no wrangler version was found

v3.6.0

Minor Changes

• #235 0545ad285acaff2b92053d636ee17fb303b4c5f5 Thanks @​AdiRishi! - wrangler-action will now re-use existing wrangler installations when available

v3.5.0

Minor Changes

• #255 31a6263ef3ec73ff2d03cb4c0260379f96f7598c Thanks @​matthewdavidrodgers! - Stop racing secret uploads

  For up to date versions of wrangler, secrets are uploaded via the 'secret:bulk' command, which batches updates in a single API call.

  For versions of wrangler without that capability, the action falls back to the single 'secret put' command for each secret. It races all these with a Promise.all()

  Unfortunately, the single secret API cannot handle concurrency - at best, these calls have to wait on one another, holding requests open all the while. Often it times out and errors.

  This fixes the legacy secret upload errors by making these calls serially instead of concurrently.

Changelog

Sourced from cloudflare/wrangler-action's changelog.

Changelog

3.6.1

Patch Changes

• #265 2d275a8f2d279dc91912c1ff8023af109ef3280c Thanks @​Maximo-Guk! - Reverts #235 which may have caused the latest version of wrangler to be installed, if no wrangler version was found

3.6.0

Minor Changes

• #235 0545ad285acaff2b92053d636ee17fb303b4c5f5 Thanks @​AdiRishi! - wrangler-action will now re-use existing wrangler installations when available

3.5.0

Minor Changes

• #255 31a6263ef3ec73ff2d03cb4c0260379f96f7598c Thanks @​matthewdavidrodgers! - Stop racing secret uploads

  For up to date versions of wrangler, secrets are uploaded via the 'secret:bulk' command, which batches updates in a single API call.

  For versions of wrangler without that capability, the action falls back to the single 'secret put' command for each secret. It races all these with a Promise.all()

  Unfortunately, the single secret API cannot handle concurrency - at best, these calls have to wait on one another, holding requests open all the while. Often it times out and errors.

  This fixes the legacy secret upload errors by making these calls serially instead of concurrently.

3.4.1

Patch Changes

• #227 bbedd8e54f256d36f81f81f1f05b90937d533bb7 Thanks @​AdiRishi! - Surface inner exception when secret:bulk upload command fails

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.

... (truncated)

Commits

• a08dc76 Automatic compilation
• b84268f Merge pull request #268 from cloudflare/changeset-release/main
• d1b97eb Version Packages
• baf8bc6 Merge pull request #265 from Maximo-Guk/maximo/revert-235
• 8edd152 Update CODEOWNERS (#266)
• 2d275a8 Revert "(feat): Use existing wrangler installation when appropriate (#235)"
• 8ef515f Version Packages (#262)
• 9b27cf2 Bump undici from 5.28.3 to 5.28.4 (#249)
• 405a826 Bump vite from 5.0.12 to 5.2.8 (#248)
• 0545ad2 (feat): Use existing wrangler installation when appropriate (#235)
• 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 <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

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

[Razzmatazzz]

.deploy

[github-actions]

Deployment Triggered 🚀

Razzmatazzz, started a branch deployment to production

You can watch the progress here 🔗

Branch: dependabot/github_actions/github-actions-d1aa20b6d5

[github-actions]

API Deployment - Production 🌔

The API has been deployed to the production environment 🚀

• Endpoint: api.tarkov.dev/graphql
• Playground: api.tarkov.dev

Pusher: @Razzmatazzz, Action: issue_comment, Workflow: branch-deploy;

[github-actions]

Deployment Results ✅

Razzmatazzz successfully deployed branch dependabot/github_actions/github-actions-d1aa20b6d5 to production

Environment URL: api.tarkov.dev/graphql