Bump the npm-dependencies group with 5 updates

[dependabot]

Bumps the npm-dependencies group with 5 updates:

Package	From	To
@graphql-tools/merge	9.0.1	9.0.3
@graphql-tools/schema	10.0.2	10.0.3
newman	6.1.0	6.1.1
prettier	3.2.4	3.2.5
wrangler	3.26.0	3.30.1

Updates @graphql-tools/merge from 9.0.1 to 9.0.3

Changelog

Sourced from @​graphql-tools/merge's changelog.

9.0.3

Patch Changes

• #5913 83c0af0 Thanks @​enisdenjo! - dependencies updates:
  • Updated dependency @graphql-tools/utils@^10.0.13 ↗︎ (from ^10.0.10, in dependencies)

9.0.2

Patch Changes

• 8880c78 Thanks @​ardatan! - Merge directive arguments

Commits

• f59d7d7 chore(release): update monorepo packages versions (#5929)
• 83c0af0 No unnecessary inline fragment spreads for union types in federation and link...
• 51b9b0b chore(release): update monorepo packages versions (#5919)
• 8880c78 enhance(merge): merge directive arguments
• See full diff in compare view

Updates @graphql-tools/schema from 10.0.2 to 10.0.3

Changelog

Sourced from @​graphql-tools/schema's changelog.

10.0.3

Patch Changes

• #5913 83c0af0 Thanks @​enisdenjo! - dependencies updates:
  • Updated dependency @graphql-tools/utils@^10.0.13 ↗︎ (from ^10.0.10, in dependencies)
• Updated dependencies [83c0af0]:
  • @​graphql-tools/merge@​9.0.3

Commits

• f59d7d7 chore(release): update monorepo packages versions (#5929)
• 83c0af0 No unnecessary inline fragment spreads for union types in federation and link...
• 4de454c Fix 'warn' for requireResolversToMatchSchema (#5775)
• See full diff in compare view

Updates newman from 6.1.0 to 6.1.1

Changelog

Sourced from newman's changelog.

6.1.1: date: 2024-02-05 chores: - Updated dependencies

Commits

• 903cc8e Merge branch 'release/6.1.1'
• 95655e6 Release v6.1.1
• 94ec971 Update dependencies
• 2c2121c Merge branch 'release/6.1.0' into develop
• See full diff in compare view

Updates prettier from 3.2.4 to 3.2.5

Release notes

Sourced from prettier's releases.

3.2.5

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.2.5

diff

Support Angular inline styles as single template literal (#15968 by @​sosukesuzuki)

Angular v17 supports single string inline styles.

// Input
@Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}
// Prettier 3.2.4
@​Component({
template: &lt;div&gt;...&lt;/div&gt;,
styles: h1 { color: blue; },
})
export class AppComponent {}
// Prettier 3.2.5
@​Component({
template: &lt;div&gt;...&lt;/div&gt;,
styles: h1 { color: blue; },
})
export class AppComponent {}

Unexpected embedded formatting for Angular template (#15969 by @​JounQin)

Computed template should not be considered as Angular component template

// Input
const template = "foobar";
@​Component({
[template]: <h1>{{       hello }}</h1>,
})
export class AppComponent {}
</tr></table>

... (truncated)

Commits

• 7142cf3 Release 3.2.5
• 8cbee2e chore(deps): update glimmer to v0.88.1 (#15991)
• 45baee0 chore(deps): update dependency magic-string to v0.30.6 (#16022)
• 9fb32a1 Minor refactor to property print (#15924)
• 08f1940 Update install script for husky v9 (#16000)
• 6d0b1d2 Update yarn to v4.1.0 (#16021)
• c8ba8db chore(deps): update dependency @​angular/compiler to v17.1.2 (#16018)
• e2250ec chore(deps): update typescript-eslint to v6.20.0 (#16015)
• 02865f6 chore(deps): update dependency npm-run-all2 to v6.1.2 (#16017)
• 014ee5d chore(deps): update dependency hermes-parser to v0.19.0 (#16014)
• Additional commits viewable in compare view

Updates wrangler from 3.26.0 to 3.30.1

Release notes

Sourced from wrangler's releases.

[email protected]

Patch Changes

• #5106 2ed7f32 Thanks @​RamIdeas! - fix: automatically drain incoming request bodies

  Previously, requests sent to wrangler dev with unconsumed bodies could result in Network connection lost errors. This change attempts to work around the issue by ensuring incoming request bodies are drained if they're not used. This is a temporary fix whilst we try to address the underlying issue. Whilst we don't think this change will introduce any other issues, it can be disabled by setting the WRANGLER_DISABLE_REQUEST_BODY_DRAINING=true environment variable. Note this fix is only applied if you've enabled Wrangler's bundling—--no-bundle mode continues to have the previous behaviour.

• #5107 65d0399 Thanks @​penalosa! - fix: Ensures that switching to remote mode during a dev session (from local mode) will correctly use the right zone. Previously, zone detection happened before the dev session was mounted, and so dev sessions started with local mode would have no zone inferred, and would have failed to start, with an ugly error.

• #5107 65d0399 Thanks @​penalosa! - fix: Ensure that preview sessions created without a zone don't switch the host on which to start the preview from the one returned by the API.

• #4833 54f6bfc Thanks @​admah! - fix: remove extra arguments from wrangler init deprecation message and update recommended c3 version

  c3 can now infer the pre-existing type from the presence of the --existing-script flag so we can remove the extra type argument. C3 2.5.0 introduces an auto-update feature that will make sure users get the latest minor version of c3 and prevent problems where older 2.x.x versions get cached by previous runs of wrangler init.

[email protected]

Minor Changes

• #4742 c2f3f1e Thanks @​benycodes! - feat: allow preserving file names when defining rules for non-js modules

  The developer is now able to specify the `preserve_file_names property in wrangler.toml which specifies whether Wrangler will preserve the file names additional modules that are added to the deployment bundle of a Worker.

  If not set to true, files will be named using the pattern ${fileHash}-${basename}. For example, 34de60b44167af5c5a709e62a4e20c4f18c9e3b6-favicon.ico.

  Resolves #4741

Patch Changes

• Updated dependencies [0c0949d]:
  • [email protected]

[email protected]

Minor Changes

• #5042 5693d076 Thanks @​dario-piotrowicz! - feat: add new --env-interface to wrangler types

  Allow users to specify the name of the interface that they want wrangler types to generate for the env parameter, via the new CLI flag --env-interface

  Example:

  wrangler types --env-interface CloudflareEnv

  generates

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.30.1

Patch Changes

• #5106 2ed7f32 Thanks @​RamIdeas! - fix: automatically drain incoming request bodies

  Previously, requests sent to wrangler dev with unconsumed bodies could result in Network connection lost errors. This change attempts to work around the issue by ensuring incoming request bodies are drained if they're not used. This is a temporary fix whilst we try to address the underlying issue. Whilst we don't think this change will introduce any other issues, it can be disabled by setting the WRANGLER_DISABLE_REQUEST_BODY_DRAINING=true environment variable. Note this fix is only applied if you've enabled Wrangler's bundling—--no-bundle mode continues to have the previous behaviour.

• #5107 65d0399 Thanks @​penalosa! - fix: Ensures that switching to remote mode during a dev session (from local mode) will correctly use the right zone. Previously, zone detection happened before the dev session was mounted, and so dev sessions started with local mode would have no zone inferred, and would have failed to start, with an ugly error.

• #5107 65d0399 Thanks @​penalosa! - fix: Ensure that preview sessions created without a zone don't switch the host on which to start the preview from the one returned by the API.

• #4833 54f6bfc Thanks @​admah! - fix: remove extra arguments from wrangler init deprecation message and update recommended c3 version

  c3 can now infer the pre-existing type from the presence of the --existing-script flag so we can remove the extra type argument. C3 2.5.0 introduces an auto-update feature that will make sure users get the latest minor version of c3 and prevent problems where older 2.x.x versions get cached by previous runs of wrangler init.

3.30.0

Minor Changes

• #4742 c2f3f1e Thanks @​benycodes! - feat: allow preserving file names when defining rules for non-js modules

  The developer is now able to specify the `preserve_file_names property in wrangler.toml which specifies whether Wrangler will preserve the file names additional modules that are added to the deployment bundle of a Worker.

  If not set to true, files will be named using the pattern ${fileHash}-${basename}. For example, 34de60b44167af5c5a709e62a4e20c4f18c9e3b6-favicon.ico.

  Resolves #4741

Patch Changes

• Updated dependencies [0c0949d]:
  • [email protected]

3.29.0

Minor Changes

• #5042 5693d076 Thanks @​dario-piotrowicz! - feat: add new --env-interface to wrangler types

  Allow users to specify the name of the interface that they want wrangler types to generate for the env parameter, via the new CLI flag --env-interface

  Example:

  wrangler types --env-interface CloudflareEnv

... (truncated)

Commits

• 5b11492 Version Packages (#5116)
• 65d0399 Better messaging in remote mode (#5107)
• 2ed7f32 Workaround "Error: Network connection lost." in POSTs from workerd to workerd...
• 54f6bfc fix: remove extra arguments from wrangler init deprecation message and update...
• 45b14fc Version Packages (#5079)
• c2f3f1e Implemented preserve_file_names config (#4742)
• 99508bf Version Packages (#5061)
• 5693d07 Add wrangler types customization and improvements (#5042)
• 1c46028 Avoid blocking built-in node modules when using --no-bundle flag (#4303)
• 50f93bd Remove stripping .py extensions and bump workerd version (#4957)
• 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]

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