Repository navigation
fix: bump non-breaking dependencies to latest - #753
Merged
Merged
Conversation
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated non-major dependency bump (deps-train).
package.json
packages/static-server/package.json
packages/bundlesize/package.json
packages/bundlecheck/package.json
Transitive refresh (
pnpm update) — 15 package(s) movedShow transitive changes
What changed
@biomejs/biome2.6.6 → 2.6.8[Biome CLI v2.6.8
](https://github.com/biomejs/biome/releases/tag/%40biomejs/biome%402.6.8)
2.6.8
Patch Changes
#13080
a68137dThanks @dyc3! - Added the nursery rulenoBufferConstructor, which disallows the deprecated Node.jsBuffer()andnew Buffer()constructors. UseBuffer.from(),Buffer.alloc(), orBuffer.allocUnsafe()instead.#12966
82651f5Thanks @dyc3! - Added the nursery rulenoConfusingArraySplice, which reportssplice()andtoSpliced()calls that replace a single element or insert at index-1.#12924
0a9d204Thanks @dyc3! - Added the nursery rulenoDynamicRequire, which disallowsrequire()calls whose module name is built at runtime. When thecheckDynamicImportsoption is enabled, the rule also checksimport()calls.…notes truncated.
[Biome CLI v2.6.7
](https://github.com/biomejs/biome/releases/tag/%40biomejs/biome%402.6.7)
2.6.7
Patch Changes
#12906
b3375d2Thanks @dyc3! - Added the nursery rulenoAsyncPromiseFinally, which reports async functions passed to a promise's.finally()method. If such a function fails, its error replaces the original result or error of the promise.#12894
e24da6fThanks @dyc3! - Added the nursery rulenoDuplicateTypeConstituents, which reports types listed more than once in a union or intersection type, andundefinedin the type of an optional parameter.#12899
6c15027Thanks @dyc3! - Added the nursery rulenoExcessiveSelectorComplexity, which limits how many IDs, type selectors, attribute selectors, pseu…notes truncated.
compare 2.6.6…2.6.8 · npm
lint-staged17.6.0 → 17.6.1v17.6.1
Patch Changes
18bc32f- The warning about the temporary patch file containing hidden partially-staged changes is only displayed when restoring the changes failed.compare 17.6.0…17.6.1 · npm
turbo2.11.10 → 2.11.11Turborepo v2.11.11
What's Changed
Changelog
@github-actions[bot] in chore: Release Turborepo 2.11.10 vercel/turborepo#14877@anthonyshewin fix: Remove redundant task disclaimers from setup output vercel/turborepo#14870@anthonyshewin fix: Report declared package manager versions in turbo info vercel/turborepo#14830.turbo/to be Git-ignored in turbo setup by@anthonyshewin feat: Stop requiring.turbo/to be Git-ignored in turbo setup vercel/turborepo#14822@anthonyshewin fix: Isolate JS test fixture cleanup between suites vercel/turborepo#14864@anthonyshewin fix: Remove Linux host version fingerprints from Python caching vercel/turborepo#14861@PedroRosalbain fix: Write the restore manifest before a local cache restore returns vercel/turborepo#14872@anthonyshewin fix: Handle SIGHUP in the npm wrapper vercel/turborepo#14856@anthonyshewin fix: Keep remote cache reads when uploads are forbidden or the token is read-only vercel/turborepo#14797@anthonyshewin fix: Discover new workspace packages in watch mode vercel/turborepo#14858turbo setupby@anthonyshewin refactor: Remove verify-system fromturbo setupvercel/turborepo#14821…notes truncated.
compare 2.11.10…2.11.11 · npm
pnpm12.19.0 → 12.21.0pnpm 12.21
pnpm 12.21.0 lets
pnpm store addprepare tarball and git dependencies for offline installs. It also makes repeated installs keep their peer dependency choices and fixes severallockfile.format: v13,nodeLinker: hoisted, andpnpm deployfailures. If a pnpr server refuses a setting, pnpm now resolves locally.Minor Changes
pnpm store addrun in a project now prepares downloaded tarballs for every lockfile entry that pins them. Besides registry packages,pnpm install --offline --frozen-lockfilecan then install dependencies on a tarball URL and dependencies on a git host such as GitHub whose lockfile entry records anintegrity.Patch Changes
Installs that failed
pnpm now reads a lockfile with a mapping key longer than 1,024 characters written as
'key':, without the?marker. Before,pnpm installand other commands failed on such a lockfile withERR_PNPM_BROKEN_LOCKFILE.With
lockfile.format: v13,pnpm installno longer fails to create or rewrite the lockfile when a package declares many of its dependencies as peers.Fixed
pnpm deployfailing withlockfile.format: v13when injected workspace packages have hashed peer bindings.Frozen installs with v13 lockfiles now accept valid peer dependencies of injected workspace packages that use catalogs.
Fixed injected workspace packages that depend on themselves linking to a nonexistent directory.
pnpm installwithfrozenStoreenabled no longer fai…notes truncated.
pnpm 12.20
pnpm 12.20.0 records the specifiers of local directory dependencies in the experimental v13 lockfile and fixes several
nodeLinker: hoisted, peer dependency, andoverridesbugs. The bundlednode-gypno longer ships the undici version that security scanners flag. Remote resolution and shared build caches no longer work with pnpr 0.1.0-alpha.19 or older.Minor Changes
lockfile.format: v13,pnpm installrecords the dependency specifiers of local directory packages. Frozen installs reject changed specifiers even when the locked versions still satisfy them.Patch Changes
Upgrading and security
Remote resolution, shared build caches, and release notes no longer work with pnpr 0.1.0-alpha.19 or older. pnpm now reads the capabilities a pnpr server advertises under
pnpr.protocols. Installs fail when the server does not confirm the requested resolution and verification policies.The
node-gypbundled with pnpm no longer ships undici 6, which security scanners flag for CVE-2026-84947. On Node.js 26,node-gypdownloads through a proxy or with a custom CA file no longer crash with "invalid onError method" #17941.Resolving dependencies
Version-selector
overridesentries such as"ms@^2.0.0": "2.1.1"now apply to dependencies declared with thecatalog:protocol when the catalog entry's range matches the selector #17922.A r
…notes truncated.
compare 12.19.0…12.21.0 · npm
@fastify/caching9.0.5 → 9.0.6v9.0.6
What's Changed
@dependabot[bot] in chore: bump fastify/workflows/.github/workflows/reusable-release.yml from b1a11bce713bc857e52b2231fec3c89071ad3135 to 731d0cca9a6a5b9586dad6b0326d49001ab9216f fastify/fastify-caching#203@TalhaHunter101in fix: apply configured Cache-control header on 304 responses fastify/fastify-caching#205New Contributors
@TalhaHunter101made their first contribution in fix: apply configured Cache-control header on 304 responses fastify/fastify-caching#205Full Changelog: fastify/fastify-caching@v9.0.5...v9.0.6
compare 9.0.5…9.0.6 · npm
@fastify/cors11.4.1 → 11.4.3v11.4.3
What's Changed
@lprnmnsin fix: normalize dynamic origin wildcard arrays fastify/fastify-cors#420Behavior note
An
originarray containing'*'is now treated as a wildcard also when it comes from a dynamic resolver (async or callbackoriginfunction) or from a route-levelconfig.cors. These cases now respond withAccess-Control-Allow-Origin: *, as the staticorigin: ['*']option already did. Previously the header was omitted.If a dynamic origin list of yours contains
'*'unintentionally, remove it before upgrading.New Contributors
@lprnmnsmade their first contribution in fix: normalize dynamic origin wildcard arrays fastify/fastify-cors#420Full Changelog: fastify/fastify-cors@v11.4.2...v11.4.3
v11.4.2
What's Changed
#428) by@JayashreeChelladuraiin fix: skip origin resolution when route disables cors (#428) fastify/fastify-cors#430New Contributors
@JayashreeChelladuraimade their first contribution in fix: skip origin resolution when route disables cors (#428) fastify/fastify-cors#430Full Changelog: fastify/fastify-cors@v11.4.1...v11.4.2
compare 11.4.1…11.4.3 · npm
@fastify/static10.1.10 → 10.1.11v10.1.11
What's Changed
@TalhaHunter101in fix: preserve directory index root priority when wildcard is false fastify/fastify-static#618With
wildcard: falseand multiple roots, directory index routes are now served from the first root that provides an index file, consistent with wildcard mode.New Contributors
@TalhaHunter101made their first contribution in fix: preserve directory index root priority when wildcard is false fastify/fastify-static#618Full Changelog: fastify/fastify-static@v10.1.10...v10.1.11
compare 10.1.10…10.1.11 · npm
glob14.0.4 → 14.0.6v14.0.6
ignorepatterns lack the braceExpandMax limit applied topatternFixes GHSA-qxr8-q827-836c: GHSA-qxr8-q827-836c
compare 14.0.4…14.0.6 · npm
better-sqlite313.0.3 → 13.2.0v13.2.0
What's Changed
/proc/self/mapsinstead of callingprocess.report.getReport(). The old method could hang on reverse DNS lookups (#1527) and gave the wrong answer under some runtimes (#1517). It's kept only as a fallback, with network lookups disabled.@kevin9327in fix: throw if unsafeMode() is called on a closed database WiseLibs/better-sqlite3#1533@everett1992in load locally compiled binaries before prebuilt binaries WiseLibs/better-sqlite3#1521better-sqlite3as a normal dependency and compile it from apostinstallscript. The local build is then used instead of the prebuilt binary.New Contributors
@kevin9327made their first contribution in fix: throw if unsafeMode() is called on a closed database WiseLibs/better-sqlite3#1533@everett1992made their first contribution in load locally compiled binaries before prebuilt binaries WiseLibs/better-sqlite3#1521Full Changelog:
WiseLibs/better-sqlite3@v13.1.1...v13.2.0
v13.1.1
What's Changed
ubuntu-24.04-armrunner image for Alpine arm64 builds by@m4heshdin Useubuntu-24.04-armrunner image for Alpine arm64 builds WiseLibs/better-sqlite3#1511@JoshuaWisein Update SQLite to version 3.54.1 WiseLibs/better-sqlite3#1531v13.1.0by@m4heshdin Upgrade node-gyp tov13.1.0WiseLibs/better-sqlite3#1532Full Changelog: WiseLibs/better-sqlite3@v13.0.3...v13.1.1
v13.1.0
Windows Arm64 build is currently failing. Stick with
v13.0.3till#1532is merged.What's Changed
ubuntu-24.04-armrunner image for Alpine arm64 builds by@m4heshdin Useubuntu-24.04-armrunner image for Alpine arm64 builds WiseLibs/better-sqlite3#1511@JoshuaWisein Update SQLite to version 3.54.1 WiseLibs/better-sqlite3#1531Full Changelog: WiseLibs/better-sqlite3@v13.0.3...v13.1.0
compare 13.0.3…13.2.0 · npm