Skip to content

Bump the dependencies group across 4 directories with 4 updates #211

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Dec 19, 2024
Merged

Bump the dependencies group across 4 directories with 4 updates #211

merged 1 commit into from
Dec 19, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 19, 2024

Bumps the dependencies group with 4 updates in the / directory: next, wrangler, eslint-config-next and @cloudflare/vitest-pool-workers.
Bumps the dependencies group with 2 updates in the /cms-data-fetcher directory: wrangler and @cloudflare/vitest-pool-workers.
Bumps the dependencies group with 2 updates in the /ogp-data-fetcher directory: wrangler and @cloudflare/vitest-pool-workers.
Bumps the dependencies group with 3 updates in the /pages directory: next, wrangler and eslint-config-next.

Updates next from 15.1.1 to 15.1.2

Release notes

Sourced from next's releases.

v15.1.2

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

Credits

Huge thanks to @​ztanner for helping!

Commits

Updates wrangler from 3.97.0 to 3.98.0

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

  • #7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets. These assets will be served as though the assets directly were mounted to the root. For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

  • #7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

  • #7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

    Adds a Wrangler API to find and read a config file

  • #7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

    • Detect Pages & Workers CI
    • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

  • #7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

Changelog

Sourced from wrangler's changelog.

3.98.0

Minor Changes

  • #7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets. These assets will be served as though the assets directly were mounted to the root. For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

  • #7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

  • #7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

    Adds a Wrangler API to find and read a config file

  • #7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

    • Detect Pages & Workers CI
    • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

  • #7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

Commits

Updates eslint-config-next from 15.1.1 to 15.1.2

Release notes

Sourced from eslint-config-next's releases.

v15.1.2

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

Credits

Huge thanks to @​ztanner for helping!

Commits

Updates @cloudflare/vitest-pool-workers from 0.5.38 to 0.5.39

Release notes

Sourced from @​cloudflare/vitest-pool-workers's releases.

@​cloudflare/vitest-pool-workers@​0.5.39

Patch Changes

Changelog

Sourced from @​cloudflare/vitest-pool-workers's changelog.

0.5.39

Patch Changes

Commits

Updates wrangler from 3.97.0 to 3.98.0

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

  • #7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets. These assets will be served as though the assets directly were mounted to the root. For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

  • #7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

  • #7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

    Adds a Wrangler API to find and read a config file

  • #7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

    • Detect Pages & Workers CI
    • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

  • #7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

Changelog

Sourced from wrangler's changelog.

3.98.0

Minor Changes

  • #7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets. These assets will be served as though the assets directly were mounted to the root. For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

  • #7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

  • #7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

    Adds a Wrangler API to find and read a config file

  • #7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

    • Detect Pages & Workers CI
    • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

  • #7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

Commits

Updates @cloudflare/vitest-pool-workers from 0.5.38 to 0.5.39

Release notes

Sourced from @​cloudflare/vitest-pool-workers's releases.

@​cloudflare/vitest-pool-workers@​0.5.39

Patch Changes

Changelog

Sourced from @​cloudflare/vitest-pool-workers's changelog.

0.5.39

Patch Changes

Commits

Updates wrangler from 3.97.0 to 3.98.0

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

  • #7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets. These assets will be served as though the assets directly were mounted to the root. For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

  • #7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

  • #7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

    Adds a Wrangler API to find and read a config file

  • #7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

    • Detect Pages & Workers CI
    • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

  • #7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

Changelog

Sourced from wrangler's changelog.

3.98.0

Minor Changes

  • #7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets. These assets will be served as though the assets directly were mounted to the root. For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

  • #7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

  • #7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

    Adds a Wrangler API to find and read a config file

  • #7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

    • Detect Pages & Workers CI
    • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

  • #7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

Commits

Updates @cloudflare/vitest-pool-workers from 0.5.38 to 0.5.39

Release notes

Sourced from @​cloudflare/vitest-pool-workers's releases.

@​cloudflare/vitest-pool-workers@​0.5.39

Patch Changes

Changelog

Sourced from @​cloudflare/vitest-pool-workers's changelog.

0.5.39

Patch Changes

Commits

Updates next from 15.1.1 to 15.1.2

Release notes

Sourced from next's releases.

v15.1.2

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

Credits

Huge thanks to @​ztanner for helping!

Commits

Updates wrangler from 3.96.0 to 3.98.0

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

  • #7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets. These assets will be served as though the assets directly were mounted to the root. For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

  • #7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

  • #7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

    Adds a Wrangler API to find and read a config file

  • #7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

    • Detect Pages & Workers CI
    • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

  • #7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

Changelog

Sourced from wrangler's changelog.

3.98.0

Minor Changes

  • #7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets. These assets will be served as though the assets directly were mounted to the root. For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

  • #7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

  • #7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

    Adds a Wrangler API to find and read a config file

  • #7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

    • Detect Pages & Workers CI
    • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

  • #7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

Commits

Updates eslint-config-next from 15.1.1 to 15.1.2

Release notes

Sourced from eslint-config-next's releases.

v15.1.2

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

Credits

Huge thanks to @​ztanner for helping!

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

@dependabot
Bump the dependencies group across 4 directories with 4 updates
c1bc195 
Bumps the dependencies group with 4 updates in the / directory: [next](https://github.com/vercel/next.js), [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler), [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) and [@cloudflare/vitest-pool-workers](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/vitest-pool-workers).
Bumps the dependencies group with 2 updates in the /cms-data-fetcher directory: [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) and [@cloudflare/vitest-pool-workers](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/vitest-pool-workers).
Bumps the dependencies group with 2 updates in the /ogp-data-fetcher directory: [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) and [@cloudflare/vitest-pool-workers](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/vitest-pool-workers).
Bumps the dependencies group with 3 updates in the /pages directory: [next](https://github.com/vercel/next.js), [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) and [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next).


Updates `next` from 15.1.1 to 15.1.2
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v15.1.1...v15.1.2)

Updates `wrangler` from 3.97.0 to 3.98.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)

Updates `eslint-config-next` from 15.1.1 to 15.1.2
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](https://github.com/vercel/next.js/commits/v15.1.2/packages/eslint-config-next)

Updates `@cloudflare/vitest-pool-workers` from 0.5.38 to 0.5.39
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/vitest-pool-workers/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/@cloudflare/[email protected]/packages/vitest-pool-workers)

Updates `wrangler` from 3.97.0 to 3.98.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)

Updates `@cloudflare/vitest-pool-workers` from 0.5.38 to 0.5.39
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/vitest-pool-workers/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/@cloudflare/[email protected]/packages/vitest-pool-workers)

Updates `wrangler` from 3.97.0 to 3.98.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)

Updates `@cloudflare/vitest-pool-workers` from 0.5.38 to 0.5.39
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/vitest-pool-workers/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/@cloudflare/[email protected]/packages/vitest-pool-workers)

Updates `next` from 15.1.1 to 15.1.2
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v15.1.1...v15.1.2)

Updates `wrangler` from 3.96.0 to 3.98.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)

Updates `eslint-config-next` from 15.1.1 to 15.1.2
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](https://github.com/vercel/next.js/commits/v15.1.2/packages/eslint-config-next)

---
updated-dependencies:
- dependency-name: next
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: wrangler
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: eslint-config-next
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: "@cloudflare/vitest-pool-workers"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: wrangler
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@cloudflare/vitest-pool-workers"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: wrangler
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@cloudflare/vitest-pool-workers"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: next
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: wrangler
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: eslint-config-next
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Dec 19, 2024
@maretol
Copy link
Owner

maretol commented Dec 19, 2024 via email

@dependabot dependabot bot merged commit f4f321f into development Dec 19, 2024
6 checks passed
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/development/dependencies-5aa15c2db0 branch December 19, 2024 22:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@maretol