Skip to content

Bump the npm_and_yarn group across 2 directories with 14 updates - #2

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/api/npm_and_yarn-8fc8b429a9
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/api/npm_and_yarn-8fc8b429a9

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 17, 2026 •

Copy link
Copy Markdown

Bumps the npm_and_yarn group with 1 update in the /api directory: vitest.
Bumps the npm_and_yarn group with 11 updates in the /web directory:

Package From To
js-yaml 4.1.1 4.2.0
@astrojs/netlify 7.0.8 7.0.13
astro 6.3.1 6.4.6
svelte 5.55.5 5.55.7
fast-uri 3.1.0 3.1.3
fast-xml-builder 1.1.4 1.3.0
fast-xml-parser 5.6.0 5.10.1
ip-address 10.1.0 10.2.0
tar 7.5.13 7.5.20
tmp 0.2.5 0.2.7
vite 7.3.3 7.3.6

Updates vitest from 2.1.9 to 4.1.10

Release notes

Sourced from vitest's releases.

v4.1.10

   🐞 Bug Fixes

    View changes on GitHub

v4.1.9

🐞 Bug Fixes

View changes on GitHub

v4.1.8

   🐞 Bug Fixes

    View changes on GitHub

v4.1.7

   🐞 Bug Fixes

    View changes on GitHub

v4.1.6

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

... (truncated)

Commits
  • db616d2 chore: release v4.1.10 (#10718)
  • bae52b5 fix(vm): fix external module resolve error with deps optimizer query for enco...
  • a7a61e7 chore: release v4.1.9 (#10598)
  • 934b0f5 fix(pool): prevent test run hang on worker crash (#10543) [backport to v4] (#...
  • 7fb2965 fix(browser): wait for orchestrator readiness before resolving browser sessio...
  • a518019 fix: fix importOriginal with optimizer and query import [backport to v4] (#...
  • e61f2dd chore: release v4.1.8
  • e4067b3 fix(browser): disable client cdp API when allowWrite/allowExec: false [ba...
  • a09d472 chore: release v4.1.7
  • a8fd24c chore: release v4.1.6
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for vitest since your current version.


Updates js-yaml from 4.1.1 to 4.2.0

Changelog

Sourced from js-yaml's changelog.

[4.2.0] - 2026-06-01

Added

  • Added docs/safety.md with notes about processing untrusted YAML.
  • Added maxDepth (100) loader option. Not a problem, but gives a better exception instead of RangeError on stack overflow.
  • Added a loader option limiting merge sequence length. Not a problem after merge fix, but an additional restriction for safety.
  • Added sourcemaps to dist/ builds.

Changed

  • Stop resolving numbers with underscores as numeric scalars, #627.
  • Switched dev toolchains to Vite / neostandard.
  • Updated demo.
  • Reorganized tests.
  • dist/ files are no longer kept in the repository.

Fixed

  • Fix parsing of properties on the first implicit block mapping key, #62.
  • Fix trailing whitespace handling when folding flow scalar lines, #307.
  • Reject top-level block scalars without content indentation, #280.
  • Ensure numbers survive round-trip, #737.
  • Fix test coverage for issue #221.
  • Fix flow scalar trailing whitespace folding, #307.
  • Fix digits in YAML named tag handles.

Security

  • Fix potential DoS via quadratic complexity in merge - deduplicate repeated elements (makes sense for malformed files > 10K).

[3.14.2] - 2025-11-15

Security

  • Backported v4.1.1 fix to v3
Commits

Updates @astrojs/netlify from 7.0.8 to 7.0.13

Release notes

Sourced from @​astrojs/netlify's releases.

@​astrojs/netlify@​7.0.13

Patch Changes

  • #17018 1310277 Thanks @​matthewp! - Hardens remotePatterns regex generation to match canonical wildcard semantics more strictly

  • Updated dependencies []:

    • @​astrojs/underscore-redirects@​1.0.3
Changelog

Sourced from @​astrojs/netlify's changelog.

7.0.13

Patch Changes

  • #17018 1310277 Thanks @​matthewp! - Hardens remotePatterns regex generation to match canonical wildcard semantics more strictly

  • Updated dependencies []:

    • @​astrojs/underscore-redirects@​1.0.3

7.0.12

Patch Changes

  • #16693 9e6edc2 Thanks @​ArmandPhilippot! - Fixes a link in the documentation specifying where to open an issue for the adapter.

  • Updated dependencies []:

    • @​astrojs/underscore-redirects@​1.0.3

7.0.11

Patch Changes

  • Updated dependencies [f732f3c]:
    • @​astrojs/internal-helpers@​0.10.0
    • @​astrojs/underscore-redirects@​1.0.3

7.0.10

Patch Changes

  • #16661 03b8f7f Thanks @​ocavue! - Updates typescript to v6. No changes are needed from users.

  • Updated dependencies []:

    • @​astrojs/underscore-redirects@​1.0.3

7.0.9

Patch Changes

Commits

Updates astro from 6.3.1 to 6.4.6

Release notes

Sourced from astro's releases.

astro@6.4.6

Patch Changes

  • #16765 b10e86e Thanks @​fkatsuhiro! - Fixes an issue where renaming an image file while the dev server is running triggers a build error. Now Astro correctly hot-reloads the image without crashing.

  • #17026 add3df1 Thanks @​matthewp! - Hardens addAttribute to drop attribute names containing characters that are invalid per the HTML spec (", ', >, /, =, whitespace)

  • #17033 ffda27b Thanks @​matthewp! - Validates the request origin against allowedDomains before fetching prerendered error pages. When allowedDomains is configured and the Host header matches, the original origin is used. Otherwise, the fetch falls back to localhost.

astro@6.4.5

Patch Changes

  • #16985 4ecff32 Thanks @​maximslo! - Fixes the experimental.logger destination not being used for the "Server listening on..." startup message. The logger is now resolved before the server starts listening, and adapterLogger re-creates itself when the underlying logger changes so the startup message uses the correct destination.

  • #16947 e0703a6 Thanks @​ematipico! - Fixes Astro.request.url not reflecting validated X-Forwarded-Proto/X-Forwarded-Host headers when security.allowedDomains is configured. Previously, only Astro.url was updated with the forwarded origin while Astro.request.url retained the socket-derived URL, causing the two to diverge behind TLS-terminating proxies.

  • #16997 dc45246 Thanks @​matthewp! - Reverts a change to isNode runtime detection that caused a significant build time regression for Cloudflare adapter users with large prerendered sites

Changelog

Sourced from astro's changelog.

6.4.6

Patch Changes

  • #16765 b10e86e Thanks @​fkatsuhiro! - Fixes an issue where renaming an image file while the dev server is running triggers a build error. Now Astro correctly hot-reloads the image without crashing.

  • #17026 add3df1 Thanks @​matthewp! - Hardens addAttribute to drop attribute names containing characters that are invalid per the HTML spec (", ', >, /, =, whitespace)

  • #17033 ffda27b Thanks @​matthewp! - Validates the request origin against allowedDomains before fetching prerendered error pages. When allowedDomains is configured and the Host header matches, the original origin is used. Otherwise, the fetch falls back to localhost.

6.4.5

Patch Changes

  • #16985 4ecff32 Thanks @​maximslo! - Fixes the experimental.logger destination not being used for the "Server listening on..." startup message. The logger is now resolved before the server starts listening, and adapterLogger re-creates itself when the underlying logger changes so the startup message uses the correct destination.

  • #16947 e0703a6 Thanks @​ematipico! - Fixes Astro.request.url not reflecting validated X-Forwarded-Proto/X-Forwarded-Host headers when security.allowedDomains is configured. Previously, only Astro.url was updated with the forwarded origin while Astro.request.url retained the socket-derived URL, causing the two to diverge behind TLS-terminating proxies.

  • #16997 dc45246 Thanks @​matthewp! - Reverts a change to isNode runtime detection that caused a significant build time regression for Cloudflare adapter users with large prerendered sites

6.4.4

Patch Changes

  • #16926 1b39ae8 Thanks @​narendraio! - Prevents App.match() from throwing on request paths that contain an invalid percent-sequence.

  • #16924 2c0bc94 Thanks @​astrobot-houston! - Fixes an issue where editing a client-side component (e.g. with client:idle, client:load, etc.) caused an unnecessary full program reload of the backend during development.

  • #16958 2c1d50f Thanks @​fkatsuhiro! - Fixes a bug where static file endpoints using getStaticPaths with .html in dynamic param values (e.g. { path: 'file.html' }) would fail with a NoMatchingStaticPathFound error during build. The .html suffix is no longer incorrectly stripped from endpoint route pathnames.

  • #16855 c610cda Thanks @​astrobot-houston! - Fixes dynamic routes returning 500 "TypeError: Missing parameter" when using domain-based i18n routing in SSR.

  • #16946 606c37b Thanks @​ematipico! - Fixes Astro.routePattern to preserve original casing of dynamic parameter names from filenames. Previously, a file at src/pages/blog/[postId].astro would return /blog/[postid] for Astro.routePattern due to an internal .toLowerCase() call. It now correctly returns /blog/[postId].

  • #16720 16d49b6 Thanks @​thomas-callahan-collibra! - Fix an issue where dynamic routes would return the string [object Object] instead of the expected content, in certain runtimes.

  • #16703 17390a6 Thanks @​henrybrewer00-dotcom! - Fixes styles being stripped when the project root is started with a path whose case differs from the actual filesystem case (e.g. running astro dev from d:\dev\app while the folder on disk is D:\dev\app).

  • #16855 c610cda Thanks @​astrobot-houston! - Fixes Astro.currentLocale returning the default locale instead of the domain's locale on dynamic routes served from a mapped domain.

6.4.3

Patch Changes

  • #16900 17a0fbd Thanks @​ocavue! - Bumps devalue dependency to v5.8.1

  • #16016 0d85e1b Thanks @​felmonon! - Fix a false positive in the dev toolbar accessibility audit for anchors with text inside closed <details> elements.

  • #16911 79c6c46 Thanks @​astrobot-houston! - Fixes a bug where experimental.advancedRouting with astro/hono handlers threw TypeError: Cannot read properties of undefined (reading 'route') for unmatched routes instead of rendering the custom 404 page.

... (truncated)

Commits

Updates svelte from 5.55.5 to 5.55.7

Release notes

Sourced from svelte's releases.

svelte@5.55.7

Patch Changes

svelte@5.55.6

Patch Changes

  • fix: leave stale promises to wait for a later resolution, instead of rejecting (#18180)

  • fix: keep dependencies of $state.eager/pending (#18218)

  • fix: reapply context after transforming error during SSR (#18099)

  • fix: don't rebase just-created batches (#18117)

  • chore: allow null for pending in typings (#18201)

  • fix: flush eager effects in production (#18107)

  • fix: rethrow error of failed iterable after calling return() (#18169)

  • fix: account for proxified instance when updating bind:this (#18147)

  • fix: ensure scheduled batch is flushed if not obsolete (#18131)

  • fix: resolve stale deriveds with latest value (#18167)

  • chore: remove unnecessary increment_pending calls (#18183)

  • fix: correctly compile component member expressions for SSR (#18192)

  • fix: reset source.updated stack traces after flush (#18196)

  • fix: replacing async 'blocking' strategy with 'merging' (#18205)

  • fix: allow @debug tags to reference awaited variables (#18138)

  • fix: re-run fallback props if dependencies update (#18146)

  • fix: abort running obsolete async branches (#18118)

... (truncated)

Changelog

Sourced from svelte's changelog.

5.55.7

Patch Changes

5.55.6

Patch Changes

  • fix: leave stale promises to wait for a later resolution, instead of rejecting (#18180)

  • fix: keep dependencies of $state.eager/pending (#18218)

  • fix: reapply context after transforming error during SSR (#18099)

  • fix: don't rebase just-created batches (#18117)

  • chore: allow null for pending in typings (#18201)

  • fix: flush eager effects in production (#18107)

  • fix: rethrow error of failed iterable after calling return() (#18169)

  • fix: account for proxified instance when updating bind:this (#18147)

  • fix: ensure scheduled batch is flushed if not obsolete (#18131)

  • fix: resolve stale deriveds with latest value (#18167)

  • chore: remove unnecessary increment_pending calls (#18183)

  • fix: correctly compile component member expressions for SSR (#18192)

  • fix: reset source.updated stack traces after flush (#18196)

  • fix: replacing async 'blocking' strategy with 'merging' (#18205)

  • fix: allow @debug tags to reference awaited variables (#18138)

  • fix: re-run fallback props if dependencies update (#18146)

... (truncated)

Commits

Updates devalue from 5.7.1 to 5.8.1

Release notes

Sourced from devalue's releases.

v5.8.1

Patch Changes

  • 206ca67: fix: force sparse arrays to allocate sparsely

v5.8.0

Minor Changes

  • c5115b0: feat: add stringifyAsync for async serialization
Changelog

Sourced from devalue's changelog.

5.8.1

Patch Changes

  • 206ca67: fix: force sparse arrays to allocate sparsely

5.8.0

Minor Changes

  • c5115b0: feat: add stringifyAsync for async serialization
Commits

Updates fast-uri from 3.1.0 to 3.1.3

Release notes

Sourced from fast-uri's releases.

v3.1.3

⚠️ Security Release

Full Changelog: fastify/fast-uri@v3.1.2...v3.1.3

v3.1.2

⚠️ Security Release

What's Changed

Full Changelog: fastify/fast-uri@v3.1.1...v3.1.2

v3.1.1

⚠️ Security Release

What's Changed

New Contributors

Full Changelog: fastify/fast-uri@v3.1.0...v3.1.1

Commits

Updates fast-xml-builder from 1.1.4 to 1.3.0

Changelog

Sourced from fast-xml-builder's changelog.

1.3.0 (2026-07-11)

  • upgrade:
    • xml-naming v0.3.0: cache support
    • PEM v1.6.2: sibling bug fix

1.2.1 (2026-07-03)

  • fix: escape quotes in stopNode attribute values (By greymoth)
  • fix: neutralize double hyphen in multi-key comment object (By spokodev)

1.2.0 (2026-05-08)

  • Add support for sanitizeName option
  • Support xml-naming for validating and sanitizing tag and attribute names

1.1.9 (2026-05-06)

  • fix: format output for preserve order when indent by is set to empty string

1.1.8 (2026-05-05)

  • fix: skip text property for PI tags
  • improve typings

1.1.7 (2026--05-04)

  • fix security issues when attribute value contains quotes

1.1.6 (2026--05-04)

  • fix security issues related to comment
  • skip comment with null value

1.1.5 (2026-04-17)

  • fix security issues related to comment and cdata

1.1.4 (2026-03-16)

  • support maxNestedTags option

1.1.3 (2026-03-13)

  • declare Matcher & Expression as unknown so user is not forced to install path-expression-matcher

1.1.2 (2026-03-11)

  • fix typings

1.1.1 (2026-03-11)

  • upgrade path-expression-matcher to 1.1.3

1.1.0 (2026-03-10)

Commits
  • 11829bf 1.3.0
  • 60774c1 browser bundle
  • 740bd54 update dependency
  • ed22f02 1.2.1
  • 9dc1fc9 update release info
  • 64808e5 Merge pull request #15 from spokodev/fix/multikey-comment-double-hyphen
  • e930f89 Merge pull request #14 from greymoth-jp/fix/stopnode-attr-escape
  • 121d93e fix: neutralize double hyphen in multi-key comment object
  • 0235eb0 fix: escape quotes in stopNode attribute values
  • e6d7c63 Update funding sources in FUNDING.yml
  • Additional commits viewable in compare view

Updates fast-xml-parser from 5.6.0 to 5.10.1

Release notes

Sourced from fast-xml-parser's releases.

v5.10.1

Full Changelog: NaturalIntelligence/fast-xml-parser@v5.10.0...v5.10.1

v5.10.0

What's Changed

Full Changelog: NaturalIntelligence/fast-xml-parser@v5.9.3...v5.10.0

v5.9.3

What's Changed

New Contributors

Full Changelog: NaturalIntelligence/fast-xml-parser@v5.9.2...v5.9.3

v5.9.2

Full Changelog: NaturalIntelligence/fast-xml-parser@v5.9.1...v5.9.2

v5.9.1

Full Changelog: NaturalIntelligence/fast-xml-parser@v5.9.0...v5.9.1

update strnum, use is-unsafe

  • update strnum to 2.3.0
    • you can set hex, binary, enotation, infinity, unicode
  • validate unsafe HTML or XML data in doctype entities unsing 'is-unsafe' library. User can override rules by overriding EntityDecoder.

update strnum, FXB. Use xml-naming for DOCTYPE

  • integrate xml-naming to validate DOCTYPE entity name and notation name (using qname because of backward compatibility)
    • This will consider xml-version as well. '1.0' is default
  • update strnum to 2.3.0
    • You can set octal and binary parsing which is by deault off
  • update fast-xml-builder to 1.2.0
    • can sanitize tag names if found invalid
    • fix format output

fix minor old bugs and update builder

  • fix: alwa...

    Description has been truncated

    Summary by CodeRabbit

    • Chores
      • Updated development and application dependencies to newer versions.
      • Improved compatibility across the API and web application tooling.

Bumps the npm_and_yarn group with 1 update in the /api directory: [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest).
Bumps the npm_and_yarn group with 11 updates in the /web directory:

| Package | From | To |
| --- | --- | --- |
| [js-yaml](https://github.com/nodeca/js-yaml) | `4.1.1` | `4.2.0` |
| [@astrojs/netlify](https://github.com/withastro/astro/tree/HEAD/packages/integrations/netlify) | `7.0.8` | `7.0.13` |
| [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) | `6.3.1` | `6.4.6` |
| [svelte](https://github.com/sveltejs/svelte/tree/HEAD/packages/svelte) | `5.55.5` | `5.55.7` |
| [fast-uri](https://github.com/fastify/fast-uri) | `3.1.0` | `3.1.3` |
| [fast-xml-builder](https://github.com/NaturalIntelligence/fast-xml-builder) | `1.1.4` | `1.3.0` |
| [fast-xml-parser](https://github.com/NaturalIntelligence/fast-xml-parser) | `5.6.0` | `5.10.1` |
| [ip-address](https://github.com/beaugunderson/ip-address) | `10.1.0` | `10.2.0` |
| [tar](https://github.com/isaacs/node-tar) | `7.5.13` | `7.5.20` |
| [tmp](https://github.com/raszi/node-tmp) | `0.2.5` | `0.2.7` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `7.3.3` | `7.3.6` |



Updates `vitest` from 2.1.9 to 4.1.10
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.10/packages/vitest)

Updates `js-yaml` from 4.1.1 to 4.2.0
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@4.1.1...4.2.0)

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

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

Updates `svelte` from 5.55.5 to 5.55.7
- [Release notes](https://github.com/sveltejs/svelte/releases)
- [Changelog](https://github.com/sveltejs/svelte/blob/main/packages/svelte/CHANGELOG.md)
- [Commits](https://github.com/sveltejs/svelte/commits/svelte@5.55.7/packages/svelte)

Updates `devalue` from 5.7.1 to 5.8.1
- [Release notes](https://github.com/sveltejs/devalue/releases)
- [Changelog](https://github.com/sveltejs/devalue/blob/main/CHANGELOG.md)
- [Commits](sveltejs/devalue@v5.7.1...v5.8.1)

Updates `fast-uri` from 3.1.0 to 3.1.3
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](fastify/fast-uri@v3.1.0...v3.1.3)

Updates `fast-xml-builder` from 1.1.4 to 1.3.0
- [Changelog](https://github.com/NaturalIntelligence/fast-xml-builder/blob/main/CHANGELOG.md)
- [Commits](NaturalIntelligence/fast-xml-builder@v1.1.4...v1.3.0)

Updates `fast-xml-parser` from 5.6.0 to 5.10.1
- [Release notes](https://github.com/NaturalIntelligence/fast-xml-parser/releases)
- [Changelog](https://github.com/NaturalIntelligence/fast-xml-parser/blob/master/CHANGELOG.md)
- [Commits](NaturalIntelligence/fast-xml-parser@v5.6.0...v5.10.1)

Updates `ip-address` from 10.1.0 to 10.2.0
- [Commits](beaugunderson/ip-address@v10.1.0...v10.2.0)

Updates `tar` from 7.5.13 to 7.5.20
- [Release notes](https://github.com/isaacs/node-tar/releases)
- [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md)
- [Commits](isaacs/node-tar@v7.5.13...v7.5.20)

Updates `tmp` from 0.2.5 to 0.2.7
- [Changelog](https://github.com/raszi/node-tmp/blob/master/CHANGELOG.md)
- [Commits](raszi/node-tmp@v0.2.5...v0.2.7)

Updates `uuid` from 11.1.0 to 13.0.0
- [Release notes](https://github.com/uuidjs/uuid/releases)
- [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md)
- [Commits](uuidjs/uuid@v11.1.0...v13.0.0)

Updates `vite` from 7.3.3 to 7.3.6
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v7.3.6/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v7.3.6/packages/vite)

---
updated-dependencies:
- dependency-name: vitest
  dependency-version: 4.1.10
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: js-yaml
  dependency-version: 4.2.0
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: "@astrojs/netlify"
  dependency-version: 7.0.13
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: astro
  dependency-version: 6.4.6
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: svelte
  dependency-version: 5.55.7
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: devalue
  dependency-version: 5.8.1
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: fast-uri
  dependency-version: 3.1.3
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: fast-xml-builder
  dependency-version: 1.3.0
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: fast-xml-parser
  dependency-version: 5.10.1
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: ip-address
  dependency-version: 10.2.0
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: tar
  dependency-version: 7.5.20
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: tmp
  dependency-version: 0.2.7
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: uuid
  dependency-version: 13.0.0
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: vite
  dependency-version: 7.3.6
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 17, 2026
@coderabbitai

coderabbitai Bot commented Jul 17, 2026 •

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Dependency version constraints are updated in the API and web package manifests, including runtime, build, deployment adapter, and test dependencies.

Changes

Dependency Version Updates

Layer / File(s) Summary
Package manifest version updates
api/package.json, web/package.json
Updated versions for js-yaml, vitest, @astrojs/netlify, astro, and svelte across API and web package manifests.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Suggested reviewers: lissy93

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the Dependabot dependency bumps across the two affected directories.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dependabot/npm_and_yarn/api/npm_and_yarn-8fc8b429a9

Comment @coderabbitai help to get the list of available commands.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​vitest@​4.1.6 ⏵ 4.1.1098 +11007998100
Updatednpm/​@​astrojs/​netlify@​7.0.8 ⏵ 7.0.1399100 +28297 +1100
Updatednpm/​svelte@​5.55.5 ⏵ 5.55.788 +1100 +688 +198100
Updatednpm/​astro@​6.3.1 ⏵ 6.4.688100 +2388 +198 +1100
Addednpm/​js-yaml@​4.2.08910010092100

View full report

@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm astro is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: web/package.json → npm/astro@6.4.6

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/astro@6.4.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm js-yaml is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: web/package.json → npm/js-yaml@4.2.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Comment thread api/package.json
Comment on lines 34 to +35
"@types/js-yaml": "^4.0.9",
"js-yaml": "^4.1.0",
"js-yaml": "^5.2.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Bug: api js-yaml jumps to major ^5.2.1, unlike web (4.2.0)

In api/package.json, js-yaml is bumped from ^4.1.0 to ^5.2.1 — a major version jump that is not reflected in the PR description (which lists only vitest for the /api directory) and is inconsistent with the same package in web/package.json, which moves to ^4.2.0. A major bump can introduce breaking API changes, and @types/js-yaml is left at ^4.0.9 (no 5.x types exist), so type definitions will no longer match the runtime library. Align the api js-yaml version with web (^4.2.0), or if the 5.x upgrade is intentional, update @types/js-yaml accordingly and verify all js-yaml usage against the 5.x API.

Keep api js-yaml on the 4.x line, consistent with web/package.json and the existing @types/js-yaml.:

"@types/js-yaml": "^4.0.9",
"js-yaml": "^4.2.0",
  • Apply fix

Check the box to apply the fix or reply for a change | Was this helpful? React with 👍 / 👎

@gitar-bot

gitar-bot Bot commented Jul 17, 2026

Copy link
Copy Markdown
Code Review ⚠️ Changes requested 0 resolved / 1 findings

Bumps the npm_and_yarn dependency group across the /api and /web directories. Changes requested because the api directory accidentally updated js-yaml to major version 5.x, creating a version mismatch with the 4.x version used in the web directory.

⚠️ Bug: api js-yaml jumps to major ^5.2.1, unlike web (4.2.0)

📄 api/package.json:34-35

In api/package.json, js-yaml is bumped from ^4.1.0 to ^5.2.1 — a major version jump that is not reflected in the PR description (which lists only vitest for the /api directory) and is inconsistent with the same package in web/package.json, which moves to ^4.2.0. A major bump can introduce breaking API changes, and @types/js-yaml is left at ^4.0.9 (no 5.x types exist), so type definitions will no longer match the runtime library. Align the api js-yaml version with web (^4.2.0), or if the 5.x upgrade is intentional, update @types/js-yaml accordingly and verify all js-yaml usage against the 5.x API.

Keep api js-yaml on the 4.x line, consistent with web/package.json and the existing @types/js-yaml.
"@types/js-yaml": "^4.0.9",
"js-yaml": "^4.2.0",
🤖 Prompt for agents
Code Review: Bumps the npm_and_yarn dependency group across the /api and /web directories. Changes requested because the api directory accidentally updated `js-yaml` to major version 5.x, creating a version mismatch with the 4.x version used in the web directory.

1. ⚠️ Bug: api js-yaml jumps to major ^5.2.1, unlike web (4.2.0)
   Files: api/package.json:34-35

   In api/package.json, js-yaml is bumped from ^4.1.0 to ^5.2.1 — a major version jump that is not reflected in the PR description (which lists only vitest for the /api directory) and is inconsistent with the same package in web/package.json, which moves to ^4.2.0. A major bump can introduce breaking API changes, and @types/js-yaml is left at ^4.0.9 (no 5.x types exist), so type definitions will no longer match the runtime library. Align the api js-yaml version with web (^4.2.0), or if the 5.x upgrade is intentional, update @types/js-yaml accordingly and verify all js-yaml usage against the 5.x API.

   Fix (Keep api js-yaml on the 4.x line, consistent with web/package.json and the existing @types/js-yaml.):
   "@types/js-yaml": "^4.0.9",
   "js-yaml": "^4.2.0",

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply Compact
gitar auto-apply:on         
gitar display:verbose         

Was this helpful? React with 👍 / 👎 | Gitar

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@api/package.json`:
- Line 40: Regenerate api/bun.lock from the updated api/package.json so Vitest
resolves to ^4.1.10 and its compatible Vite dependency, replacing the stale
vitest@2.1.9 and vite@5.4.21 entries. Verify the resulting lockfile supports bun
install --frozen-lockfile.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3531091e-5443-4682-a42a-dfefbfad1a89

📥 Commits

Reviewing files that changed from the base of the PR and between d95b761 and be5e96e.

⛔ Files ignored due to path filters (1)
  • web/yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (2)
  • api/package.json
  • web/package.json

Comment thread api/package.json
"prettier": "^3.8.3",
"typescript": "^5.7.2",
"vitest": "^2.1.8",
"vitest": "^4.1.10",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -e
node --version
yarn --cwd api why vite
yarn --cwd api vitest --version

Repository: big-main/awesome-privacy

Length of output: 347


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'Repo root files:\n'
git ls-files | sed -n '1,200p' | rg '^(api/package\.json|api/(pnpm-lock|yarn.lock|package-lock\.json)|\.github/workflows/|\.nvmrc|\.node-version|package\.json|yarn\.lock|pnpm-lock\.yaml)$' -n || true

printf '\napi/package.json:\n'
cat -n api/package.json

printf '\nWorkflow files:\n'
git ls-files .github/workflows | sed -n '1,200p' || true

Repository: big-main/awesome-privacy

Length of output: 2139


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'api CI workflow:\n'
cat -n .github/workflows/ci-api.yml

printf '\nRoot package files:\n'
git ls-files | rg '(^package\.json$|^bun\.lockb$|^bun\.lock$|^pnpm-lock\.yaml$|^yarn.lock$|^package-lock\.json$|^\.nvmrc$|^\.node-version$)' || true

printf '\nAny vite references:\n'
rg -n --hidden --glob '!**/node_modules/**' '\bvite\b' .

Repository: big-main/awesome-privacy

Length of output: 17920


🏁 Script executed:

#!/bin/bash
set -euo pipefail

cat -n .github/workflows/ci-api.yml

printf '\n---\n'
git ls-files | rg '(^package\.json$|^bun\.lockb$|^bun\.lock$|^pnpm-lock\.yaml$|^yarn.lock$|^package-lock\.json$|^\.nvmrc$|^\.node-version$)' || true

printf '\n---\n'
rg -n --hidden --glob '!**/node_modules/**' '\bvite\b' .

Repository: big-main/awesome-privacy

Length of output: 17870


🌐 Web query:

Vitest 4 requirements Node 20 Vite 6 migration documentation

💡 Result:

As of July 17, 2026, Vitest 4 has evolved its minimum requirements beyond its initial release specifications. While Vitest 4.0 was originally released requiring Node.js >= 20.0.0 and Vite >= 6.0.0 [1][2], current versions of Vitest now require Node.js >= 22.12.0 and Vite >= 6.4.0 [3][4][5]. This update was implemented to support native WebSocket functionality and align with Node.js release schedules [4]. Migration Documentation and Considerations: 1. Requirements Check: Before migrating, ensure your environment meets the current minimums (Node.js 22.12.0+ and Vite 6.4.0+) [3][4]. Running on older versions is unsupported and likely to cause errors [1]. 2. Official Migration Guide: The primary resource for upgrading is the official Vitest Migration Guide, located at https://vitest.dev/guide/migration.html [1]. It details breaking changes, such as: - Browser Mode: Provider factories are now required instead of strings (e.g., configuring providers like @vitest/browser-playwright) [6][7]. - Coverage: The coverage.all option has been removed, and the default behavior now includes only covered files in reports [7]. - Mocking: Changes to how mocks are constructed and handled [7]. - Pool Rework: Updates to environment variables and configuration options (e.g., VITEST_MAX_FORKS renamed to VITEST_MAX_WORKERS) [7]. 3. Vite 6 Migration: When moving to Vite 6, note that Vitest configures Vite to exclude the module conditional export by default, which may affect how some dependencies are resolved [8]. Consult the official Vite 6 migration documentation at https://v6.vite.dev/guide/migration for general Vite-specific breaking changes [9]. It is highly recommended to review the official changelog and migration guide specifically for the version path you are taking, as specific breaking changes may have been introduced incrementally since the initial Vitest 4.0 release [10][6].

Citations:


Sync api/bun.lock for Vitest 4. api/package.json now asks for vitest@^4.1.10, but the lockfile still resolves vitest@2.1.9 and vite@5.4.21; bun install --frozen-lockfile in API CI will fail until it’s regenerated.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@api/package.json` at line 40, Regenerate api/bun.lock from the updated
api/package.json so Vitest resolves to ^4.1.10 and its compatible Vite
dependency, replacing the stale vitest@2.1.9 and vite@5.4.21 entries. Verify the
resulting lockfile supports bun install --frozen-lockfile.

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