Skip to content

chore(deps): bump the npm-minor group with 4 updates - #22

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-minor-8df07517f9
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-minor-8df07517f9

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor

Bumps the npm-minor group with 4 updates: @astrojs/sitemap, @lhci/cli, wrangler and @astrojs/starlight.

Updates @astrojs/sitemap from 3.7.4 to 3.7.5

Release notes

Sourced from @​astrojs/sitemap's releases.

@​astrojs/sitemap@​3.7.5

Patch Changes

  • #18149 71f4d06 Thanks @​irontaek! - Speeds up sitemap chunk generation for large sites by tracking assigned URLs with a Set.
Changelog

Sourced from @​astrojs/sitemap's changelog.

3.7.5

Patch Changes

  • #18149 71f4d06 Thanks @​irontaek! - Speeds up sitemap chunk generation for large sites by tracking assigned URLs with a Set.
Commits

Updates @lhci/cli from 0.16.0 to 0.16.1

Release notes

Sourced from @​lhci/cli's releases.

v0.16.1

v0.16.1 (2026-11-11)

  • fix(cli): preserve URL hash fragments when uploading and asserting (#1201) (b0c42f4), closes #1201
  • fix(server): convert mysql tables to utf8mb4 to support 4-byte characters (#1200) (d9954d4), closes #1200
  • chore: update docker images with latest version (66c1ec2)
  • chore(deps): bump proxy-agent to ^8.0.2 (#1198) (f3322d7), closes #1198
  • misc(release): fix VERSION env export in docker job and skip_npm manifest condition (#1195) (3ead206), closes #1195
Commits
  • b0c42f4 fix(cli): preserve URL hash fragments when uploading and asserting (#1201)
  • d9954d4 fix(server): convert mysql tables to utf8mb4 to support 4-byte characters (#1...
  • 1c7b0c8 feat(utils): support ESM lighthouserc files (.mjs and "type": "module") (#1199)
  • f3322d7 chore(deps): bump proxy-agent to ^8.0.2 (#1198)
  • 3ead206 misc(release): fix VERSION env export in docker job and skip_npm manifest con...
  • 66c1ec2 chore: update docker images with latest version
  • See full diff in compare view

Updates wrangler from 4.158.0 to 4.162.0

Release notes

Sourced from wrangler's releases.

wrangler@4.162.0

Minor Changes

  • #16735 f005593 Thanks @​leostera! - Use the local simulator for Artifacts bindings that omit remote

    Behavior change: Artifacts bindings now default to the local simulator during development, like KV, R2 and D1. Previously, an omitted remote in Wrangler and the Vite plugin used the deployed Artifacts resource. If you want deployed repos in wrangler dev or vite dev, set "remote": true on the binding (dev: { remote: true } in cloudflare.config.ts). Artifacts is in beta, so this ships as a minor release.

    While remote is omitted, wrangler dev, getPlatformProxy() and the Vite plugin warn when remote bindings are enabled, once for each binding rather than on every config reload: "Artifacts binding REPOS uses the local simulator by default. Set remote: true to use deployed repos, or remote: false to silence this warning." Workers Vitest and wrangler dev --local already used the simulator, so they don't warn. Local Artifacts needs no Cloudflare credentials, but requires Git 2.32 or newer on the host.

  • #16749 032f8c2 Thanks @​vaishnav-mk! - Reject settings on a workflows binding to a Workflow declared in exports

    A workflows binding can still bind a Workflow that the Worker declares in exports, but it can no longer set limits, concurrency, schedules, default_retention, or jurisdiction for it. Set them on the export instead. Previously the binding and the export could both set them as long as they agreed, so configurations that set them on the binding now stop with an error that says which setting to move.

  • #16749 032f8c2 Thanks @​vaishnav-mk! - Upload Workflow export settings with the Worker

    wrangler deploy and wrangler versions upload now include the settings of each workflow export (limits, concurrency, schedules, default_retention, and jurisdiction) in the upload, instead of sending only its type and name. Uploads of a Worker with workflow exports also send a Cloudflare-Workers-Script-Api-Date header, which lets the Workers API provision Workflow exports from these settings as part of the upload. wrangler deploy and wrangler triggers deploy still create or update each Workflow through the Workflows API afterwards, as before.

    If provisioning a scheduled Workflow fails because the account is on the free plan, wrangler deploy now explains that scheduled Workflows require a paid Workers plan.

Patch Changes

  • #16849 3cea40b Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-12

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #16886 63eb6da Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-13

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #16849 3cea40b Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261110.1 ^5.20261112.1
    workerd 1.20261110.1 1.20261112.1
  • #16886 63eb6da Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261112.1 ^5.20261113.1
    workerd 1.20261112.1 1.20261113.1
  • #16864 3b1b408 Thanks @​MattieTK! - Fix packages with nested package.json files missing from deploy metadata

    Packages such as hono, stripe and @modelcontextprotocol/sdk were silently omitted from the package dependency metadata reported during wrangler deploy and wrangler versions upload. These packages are now included with their installed versions. Autoconfig and codemods also detect their installed versions correctly.

... (truncated)

Commits
  • 79b890a Version Packages (#16863)
  • f005593 [wrangler] Use the local Artifacts simulator when remote is omitted (#16735)
  • 032f8c2 [deploy-helpers,wrangler,codemods] Upload Workflow export settings with the W...
  • c889551 [wrangler] Fix requests hanging after local Worker reloads (#16862)
  • 1e688ba Version Packages (#16836)
  • 8b2a363 Write source maps in Build Output with sources relative to each source map ...
  • 575d136 [autoconfig] Support SolidStart 2 on cf (#16559)
  • 3626ee8 Remove CLOUDFLARE_CF_AUTH and require explicit auth for remote bindings ses...
  • 5f539b5 Name cf commands and settings in remote bindings errors (#16833)
  • 12a9105 [wrangler] Quiet E2E cleanup and preserve deployment failure output (#16832)
  • Additional commits viewable in compare view

Updates @astrojs/starlight from 0.42.10 to 0.43.1

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.43.1

Patch Changes

  • #4396 46a5020 Thanks @​trueberryless! - Fixes a regression where the icon of the <Aside> component was rendered smaller than the icon of Markdown asides.

@​astrojs/starlight@​0.43.0

Minor Changes

  • #4190 3f2336b Thanks @​delucis! - ⚠️ BREAKING CHANGE: Adds support for any Astro scopedStyleStrategy configuration.

    Previously, Starlight forced the "where" strategy, resulting in CSS selectors like :where(.astro-HASH). Starlight now respects the strategy set in astro.config.mjs and will default to Astro’s default "attribute" strategy, resulting in attribute selectors like [data-astro-cid-HASH].

    The new default can change some styling behaviour, so we recommend checking for visual changes in your site when updating. In particular, note the following:

    • Attribute selectors have a higher specificity than :where() selectors. Check to ensure styles still apply and no CSS changes are needed to ensure the relative specificity of declarations remains the same.

    • Astro’s "attribute" strategy does not automatically pass along a parent component’s scope when passing a class down to a child component. If you have components that depended on this, you will need to update the child component to spread the parent’s data attribute where you are reusing the class name, for example:

      ---
      // Parent.astro
      ---
      <Child class="special-case" />
      <style>
      .special-case {
      --accent-color: red;
      }
      </style>

      ---
      // Child.astro
      -const { class: className } = Astro.props;
      +const { class: className, ...attributes } = Astro.props;
      ---
      -<div class={className}>
      +<div class={className} {...attributes}>
      <!-- ... -->
      </div>

      See “Passing a class to a child component” in the Astro docs for more details.

    Alternatively, if you wish to continue using the previous scoping strategy in your site, set it explicitly in your Astro configuration file:

    // astro.config.mjs

... (truncated)

Changelog

Sourced from @​astrojs/starlight's changelog.

0.43.1

Patch Changes

  • #4396 46a5020 Thanks @​trueberryless! - Fixes a regression where the icon of the <Aside> component was rendered smaller than the icon of Markdown asides.

0.43.0

Minor Changes

  • #4190 3f2336b Thanks @​delucis! - ⚠️ BREAKING CHANGE: Adds support for any Astro scopedStyleStrategy configuration.

    Previously, Starlight forced the "where" strategy, resulting in CSS selectors like :where(.astro-HASH). Starlight now respects the strategy set in astro.config.mjs and will default to Astro’s default "attribute" strategy, resulting in attribute selectors like [data-astro-cid-HASH].

    The new default can change some styling behaviour, so we recommend checking for visual changes in your site when updating. In particular, note the following:

    • Attribute selectors have a higher specificity than :where() selectors. Check to ensure styles still apply and no CSS changes are needed to ensure the relative specificity of declarations remains the same.

    • Astro’s "attribute" strategy does not automatically pass along a parent component’s scope when passing a class down to a child component. If you have components that depended on this, you will need to update the child component to spread the parent’s data attribute where you are reusing the class name, for example:

      ---
      // Parent.astro
      ---
      <Child class="special-case" />
      <style>
      .special-case {
      --accent-color: red;
      }
      </style>

      ---
      // Child.astro
      -const { class: className } = Astro.props;
      +const { class: className, ...attributes } = Astro.props;
      ---
      -<div class={className}>
      +<div class={className} {...attributes}>
      <!-- ... -->
      </div>

      See “Passing a class to a child component” in the Astro docs for more details.

    Alternatively, if you wish to continue using the previous scoping strategy in your site, set it explicitly in your Astro configuration file:

... (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 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-minor group with 4 updates: [@astrojs/sitemap](https://github.com/withastro/astro/tree/HEAD/packages/integrations/sitemap), [@lhci/cli](https://github.com/GoogleChrome/lighthouse-ci), [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) and [@astrojs/starlight](https://github.com/withastro/starlight/tree/HEAD/packages/starlight).


Updates `@astrojs/sitemap` from 3.7.4 to 3.7.5
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/integrations/sitemap/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/@astrojs/sitemap@3.7.5/packages/integrations/sitemap)

Updates `@lhci/cli` from 0.16.0 to 0.16.1
- [Release notes](https://github.com/GoogleChrome/lighthouse-ci/releases)
- [Commits](GoogleChrome/lighthouse-ci@v0.16.0...v0.16.1)

Updates `wrangler` from 4.158.0 to 4.162.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.162.0/packages/wrangler)

Updates `@astrojs/starlight` from 0.42.10 to 0.43.1
- [Release notes](https://github.com/withastro/starlight/releases)
- [Changelog](https://github.com/withastro/starlight/blob/main/packages/starlight/CHANGELOG.md)
- [Commits](https://github.com/withastro/starlight/commits/@astrojs/starlight@0.43.1/packages/starlight)

---
updated-dependencies:
- dependency-name: "@astrojs/sitemap"
  dependency-version: 3.7.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-minor
- dependency-name: "@lhci/cli"
  dependency-version: 0.16.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-minor
- dependency-name: wrangler
  dependency-version: 4.162.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-minor
- dependency-name: "@astrojs/starlight"
  dependency-version: 0.43.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from jamesconwaydev as a code owner November 16, 2026 20:57
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 16, 2026
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying tachyoncms-website with  Cloudflare Pages  Cloudflare Pages

Latest commit: 6f7f4e1
Status: ✅  Deploy successful!
Preview URL: https://698cbb86.tachyoncms-website.pages.dev
Branch Preview URL: https://dependabot-npm-and-yarn-npm-xmnf.tachyoncms-website.pages.dev

View logs

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.

0 participants