Bump the npm-dependencies group with 2 updates

[dependabot]

Bumps the npm-dependencies group with 2 updates: newman and wrangler.

Updates newman from 6.1.1 to 6.1.2

Changelog

Sourced from newman's changelog.

6.1.2: date: 2024-03-14 fixed bugs: - GH-3212 Fixed a bug where --color off was not respected in summary table chores: - Updated dependencies

Commits

• 7f8f802 Merge branch 'release/6.1.2'
• 7b77e24 Release v6.1.2
• 4dec1de Merge pull request #3190 from baev/patch-1
• 4a427fd Update dependencies
• cd81df4 Merge pull request #3212 from yardenshoham/issues/3169
• bb772e5 Update colored output test regex
• 36a209d Fix --color off not being respected in summary table
• 0bcba86 Merge branch 'release/6.1.1' into develop
• 2d95c41 update Allure report site
• See full diff in compare view

Updates wrangler from 3.30.0 to 3.41.0

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

• #5425 b7a6d9d Thanks @​rozenmd! - feat: implement wrangler d1 export

[email protected]

Minor Changes

• #5426 9343714 Thanks @​RamIdeas! - feature: added a new wrangler triggers deploy command

  This command currently requires the --experimental-versions flag.

  This command extracts the trigger deployment logic from wrangler deploy and allows users to update their currently deployed Worker's triggers without doing another deployment. This is primarily useful for users of wrangler versions upload and wrangler versions deploy who can then run wrangler triggers deploy to apply trigger changes to their currently deployed Worker Versions.

  The command can also be used even if not using the wrangler versions ... commands. And, in fact, users are already using it implicitly when running wrangler deploy.

• #4932 dc0c1dc Thanks @​xortive! - feature: Add support for private networking in Hyperdrive configs

• #5369 7115568 Thanks @​mattdeboard! - fix: Use queue name, not ID, for r2 bucket event-notification subcommands

  Since the original command was not yet operational, this update does not constitute a breaking change.

  Instead of providing the queue ID as the parameter to --queue, users must provide the queue name. Under the hood, we will query the Queues API for the queue ID given the queue name.

• #5413 976adec Thanks @​pmiguel! - feature: Added Queue delivery controls support in wrangler.toml

• #5412 3e5a932 Thanks @​RamIdeas! - feature: adds the --json option to wrangler deployments list --experimental-versions, wrangler deployments status --experimental-versions, wrangler versions list --experimental-versions and wrangler versions view --experimental-versions which will format the output as clean JSON. The --experimental-versions flag is still required for these commands.

• #5258 fbdca7d Thanks @​OilyLime! - feature: URL decode components of the Hyperdrive config connection string

• #5416 47b325a Thanks @​mattdeboard! - fix: minor improvements to R2 notification subcommand

  1. r2 bucket event-notification <subcommand> becomes r2 bucket notification <subcommand>
  2. Parameters to --event-type use - instead of _ (e.g. object_create -> object-create)

  Since the original command was not yet operational, this update does not constitute a breaking change.

Patch Changes

• #5419 daac6a2 Thanks @​RamIdeas! - chore: add helpful logging to --experimental-versions commands

• #5400 c90dd6b Thanks @​RamIdeas! - chore: log of impending change of "Deployment ID" to "Version ID" in wrangler deploy, wrangler deployments list, wrangler deployments view and wrangler rollback. This is a warning of a future change for anyone depending on the output text format, for example by grepping the output in automated flows.

• #5422 b341614 Thanks @​geelen! - fix: remove d1BetaWarning and all usages

  This PR removes the warning that D1 is in beta for all D1 commands.

• Updated dependencies [fbdca7d]:

  • [email protected]

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.41.0

Minor Changes

• #5425 b7a6d9d Thanks @​rozenmd! - feat: implement wrangler d1 export

3.40.0

Minor Changes

• #5426 9343714 Thanks @​RamIdeas! - feature: added a new wrangler triggers deploy command

  This command currently requires the --experimental-versions flag.

  This command extracts the trigger deployment logic from wrangler deploy and allows users to update their currently deployed Worker's triggers without doing another deployment. This is primarily useful for users of wrangler versions upload and wrangler versions deploy who can then run wrangler triggers deploy to apply trigger changes to their currently deployed Worker Versions.

  The command can also be used even if not using the wrangler versions ... commands. And, in fact, users are already using it implicitly when running wrangler deploy.

• #4932 dc0c1dc Thanks @​xortive! - feature: Add support for private networking in Hyperdrive configs

• #5369 7115568 Thanks @​mattdeboard! - fix: Use queue name, not ID, for r2 bucket event-notification subcommands

  Since the original command was not yet operational, this update does not constitute a breaking change.

  Instead of providing the queue ID as the parameter to --queue, users must provide the queue name. Under the hood, we will query the Queues API for the queue ID given the queue name.

• #5413 976adec Thanks @​pmiguel! - feature: Added Queue delivery controls support in wrangler.toml

• #5412 3e5a932 Thanks @​RamIdeas! - feature: adds the --json option to wrangler deployments list --experimental-versions, wrangler deployments status --experimental-versions, wrangler versions list --experimental-versions and wrangler versions view --experimental-versions which will format the output as clean JSON. The --experimental-versions flag is still required for these commands.

• #5258 fbdca7d Thanks @​OilyLime! - feature: URL decode components of the Hyperdrive config connection string

• #5416 47b325a Thanks @​mattdeboard! - fix: minor improvements to R2 notification subcommand

  1. r2 bucket event-notification <subcommand> becomes r2 bucket notification <subcommand>
  2. Parameters to --event-type use - instead of _ (e.g. object_create -> object-create)

  Since the original command was not yet operational, this update does not constitute a breaking change.

Patch Changes

• #5419 daac6a2 Thanks @​RamIdeas! - chore: add helpful logging to --experimental-versions commands

• #5400 c90dd6b Thanks @​RamIdeas! - chore: log of impending change of "Deployment ID" to "Version ID" in wrangler deploy, wrangler deployments list, wrangler deployments view and wrangler rollback. This is a warning of a future change for anyone depending on the output text format, for example by grepping the output in automated flows.

• #5422 b341614 Thanks @​geelen! - fix: remove d1BetaWarning and all usages

  This PR removes the warning that D1 is in beta for all D1 commands.

• Updated dependencies [fbdca7d]:

... (truncated)

Commits

• b6ca1ae Version Packages (#5441)
• b7a6d9d [D1] initial wrangler d1 export (#5425)
• 1af469a Version Packages (#5418)
• 2d1220f Fix nits from #5426 (#5436)
• 006f1ae update snapshots (#5432)
• 976adec feat(wrangler): Queue delivery delay support in wrangler.toml (#5413)
• c234dad update snapshots (#5430)
• daac6a2 add helpful logging to --experimental-versions commands (#5419)
• 9343714 Implement triggers deploy command (#5426)
• aa22144 Implement version_metadata binding (#5421)
• 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>.

[dependabot]

Superseded by #290.