Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump the npm-dependencies group with 2 updates #299

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 1, 2024

Bumps the npm-dependencies group with 2 updates: @graphql-tools/schema and wrangler.

Updates @graphql-tools/schema from 10.0.3 to 10.0.4

Changelog

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

10.0.4

Patch Changes

Commits

Updates wrangler from 3.53.0 to 3.58.0

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

  • #5933 93b98cb Thanks @​WalshyDev! - feature: allow for writing authentication details per API environment. This allows someone targetting staging to have their staging auth details saved separately from production, this saves them logging in and out when switching environments.

Patch Changes

  • #5938 9e4d8bc Thanks @​threepointone! - fix: let "assets" in wrangler.toml be a string

    The experimental "assets" field can be either a string or an object. However the type definition marks it only as an object. This is a problem because we use this to generate the json schema, which gets picked up by vscode's even better toml extension, and shows it to be an error when used with a string (even though it works fine). The fix is to simply change the type definition to add a string variant.

  • #5758 8e5e589 Thanks @​Jackenmen! - fix: use correct type for AI binding instead of unknown

  • Updated dependencies [e0e7725]:

[email protected]

Patch Changes

[email protected]

Patch Changes

  • #5859 f2ceb3a Thanks @​w-kuhn! - fix: queue consumer max_batch_timeout should accept a 0 value

  • #5862 441a05f Thanks @​CarmenPopoviciu! - fix: wrangler pages deploy should fail if deployment was unsuccessful

    If a Pages project fails to deploy, wrangler pages deploy will log an error message, but exit successfully. It should instead throw a FatalError.

  • #5812 d5e00e4 Thanks @​thomasgauvin! - fix: remove Hyperdrive warning for local development.

    Hyperdrive bindings are now supported when developing locally with Hyperdrive. We should update our logs to reflect this.

  • #5626 a12b031 Thanks @​RamIdeas! - chore: ignore workerd output (error: CODE_MOVED) not intended for end-user devs

[email protected]

Minor Changes

  • #5696 7e97ba8 Thanks @​geelen! - feature: Improved d1 execute --file --remote performance & added support for much larger SQL files within a single transaction.

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.58.0

Minor Changes

  • #5933 93b98cb Thanks @​WalshyDev! - feature: allow for writing authentication details per API environment. This allows someone targetting staging to have their staging auth details saved separately from production, this saves them logging in and out when switching environments.

Patch Changes

  • #5938 9e4d8bc Thanks @​threepointone! - fix: let "assets" in wrangler.toml be a string

    The experimental "assets" field can be either a string or an object. However the type definition marks it only as an object. This is a problem because we use this to generate the json schema, which gets picked up by vscode's even better toml extension, and shows it to be an error when used with a string (even though it works fine). The fix is to simply change the type definition to add a string variant.

  • #5758 8e5e589 Thanks @​Jackenmen! - fix: use correct type for AI binding instead of unknown

  • Updated dependencies [e0e7725]:

3.57.2

Patch Changes

3.57.1

Patch Changes

  • #5859 f2ceb3a Thanks @​w-kuhn! - fix: queue consumer max_batch_timeout should accept a 0 value

  • #5862 441a05f Thanks @​CarmenPopoviciu! - fix: wrangler pages deploy should fail if deployment was unsuccessful

    If a Pages project fails to deploy, wrangler pages deploy will log an error message, but exit successfully. It should instead throw a FatalError.

  • #5812 d5e00e4 Thanks @​thomasgauvin! - fix: remove Hyperdrive warning for local development.

    Hyperdrive bindings are now supported when developing locally with Hyperdrive. We should update our logs to reflect this.

  • #5626 a12b031 Thanks @​RamIdeas! - chore: ignore workerd output (error: CODE_MOVED) not intended for end-user devs

3.57.0

... (truncated)

Commits

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

Bumps the npm-dependencies group with 2 updates: [@graphql-tools/schema](https://github.com/ardatan/graphql-tools/tree/HEAD/packages/schema) and [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler).


Updates `@graphql-tools/schema` from 10.0.3 to 10.0.4
- [Release notes](https://github.com/ardatan/graphql-tools/releases)
- [Changelog](https://github.com/ardatan/graphql-tools/blob/master/packages/schema/CHANGELOG.md)
- [Commits](https://github.com/ardatan/graphql-tools/commits/@graphql-tools/[email protected]/packages/schema)

Updates `wrangler` from 3.53.0 to 3.58.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/[email protected]/packages/wrangler)

---
updated-dependencies:
- dependency-name: "@graphql-tools/schema"
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: wrangler
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from a team as a code owner June 1, 2024 00:18
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jun 1, 2024
Copy link
Contributor

github-actions bot commented Jun 1, 2024

👋 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
Copy link
Member

.deploy to development

Copy link
Contributor

github-actions bot commented Jun 4, 2024

Deployment Triggered 🚀

Razzmatazzz, started a branch deployment to development

You can watch the progress here 🔗

Branch: dependabot/npm_and_yarn/npm-dependencies-a35d5cc2df

Copy link
Contributor

github-actions bot commented Jun 4, 2024

API Deployment - Development 🪐

The API has been deployed to the development environment 🚀

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

Copy link
Contributor

github-actions bot commented Jun 4, 2024

Deployment Results ✅

Razzmatazzz successfully deployed branch dependabot/npm_and_yarn/npm-dependencies-a35d5cc2df to development

Environment URL: dev-api.tarkov.dev/graphql

@Razzmatazzz
Copy link
Member

.deploy

Copy link
Contributor

github-actions bot commented Jun 4, 2024

Deployment Triggered 🚀

Razzmatazzz, started a branch deployment to production

You can watch the progress here 🔗

Branch: dependabot/npm_and_yarn/npm-dependencies-a35d5cc2df

Copy link
Contributor

github-actions bot commented Jun 4, 2024

API Deployment - Production 🌔

The API has been deployed to the production environment 🚀

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

Copy link
Contributor

github-actions bot commented Jun 4, 2024

Deployment Results ✅

Razzmatazzz successfully deployed branch dependabot/npm_and_yarn/npm-dependencies-a35d5cc2df to production

Environment URL: api.tarkov.dev/graphql

@Razzmatazzz Razzmatazzz merged commit 4114858 into main Jun 4, 2024
3 checks passed
@Razzmatazzz Razzmatazzz deleted the dependabot/npm_and_yarn/npm-dependencies-a35d5cc2df branch June 4, 2024 02:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant