chore(deps): bump the npm_and_yarn group across 5 directories with 3 updates#1871
Closed
dependabot[bot] wants to merge 1 commit into
Closed
chore(deps): bump the npm_and_yarn group across 5 directories with 3 updates#1871dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
|
Contributor
Prompt To Fix All With AIFix the following 2 code review issues. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 2
pnpm-lock.yaml:98-101
**Lock file specifier out of sync with package.json for `apps/wallets/react`**
The `pnpm-lock.yaml` records `specifier: 15.5.15` for `apps/wallets/react`, but the corresponding `package.json` specifies `"next": "^15.5.18"`. These must agree, so running `pnpm install --frozen-lockfile` (common in CI) will fail with a lockfile-mismatch error. More importantly, any install that does succeed from this lock file will resolve `15.5.15` — the version *before* the high-severity security patches (middleware/proxy bypasses, DoS, SSRF) that `15.5.16`–`15.5.18` were specifically released to fix.
### Issue 2 of 2
packages/client/base/package.json:33
**Stale `@types/uuid` dev dependency after major version upgrade**
`uuid` was bumped from `9.0.1` to `14.0.0`, but `@types/uuid` is still pinned at `9.0.4`. Starting from `uuid` v10+, the package ships its own TypeScript declarations, making `@types/uuid` unnecessary. Keeping the v9 type definitions alongside the v14 package can produce duplicate or conflicting type declarations, which may cause `tsc` errors in consuming packages.
Reviews (1): Last reviewed commit: "chore(deps): bump the npm_and_yarn group..." | Re-trigger Greptile |
Contributor
🔥 Smoke Test Results✅ Status: Passed Statistics
✅ All smoke tests passed!All critical flows are working correctly. This is a non-blocking smoke test. Full regression tests run separately. |
…updates Bumps the npm_and_yarn group with 3 updates in the / directory: [turbo](https://github.com/vercel/turborepo), [next](https://github.com/vercel/next.js) and [uuid](https://github.com/uuidjs/uuid). Bumps the npm_and_yarn group with 1 update in the /apps/auth/nextjs-ssr directory: [next](https://github.com/vercel/next.js). Bumps the npm_and_yarn group with 1 update in the /apps/payments/nextjs directory: [next](https://github.com/vercel/next.js). Bumps the npm_and_yarn group with 1 update in the /apps/wallets/quickstart-devkit directory: [next](https://github.com/vercel/next.js). Bumps the npm_and_yarn group with 1 update in the /packages/client/base directory: [uuid](https://github.com/uuidjs/uuid). Updates `turbo` from 2.2.3 to 2.9.14 - [Release notes](https://github.com/vercel/turborepo/releases) - [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md) - [Commits](vercel/turborepo@v2.2.3...v2.9.14) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `uuid` from 9.0.1 to 14.0.0 - [Release notes](https://github.com/uuidjs/uuid/releases) - [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md) - [Commits](uuidjs/uuid@v9.0.1...v14.0.0) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `turbo` from 2.2.3 to 2.9.14 - [Release notes](https://github.com/vercel/turborepo/releases) - [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md) - [Commits](vercel/turborepo@v2.2.3...v2.9.14) Updates `uuid` from 9.0.1 to 14.0.0 - [Release notes](https://github.com/uuidjs/uuid/releases) - [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md) - [Commits](uuidjs/uuid@v9.0.1...v14.0.0) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `turbo` from 2.2.3 to 2.9.14 - [Release notes](https://github.com/vercel/turborepo/releases) - [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md) - [Commits](vercel/turborepo@v2.2.3...v2.9.14) Updates `uuid` from 9.0.1 to 14.0.0 - [Release notes](https://github.com/uuidjs/uuid/releases) - [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md) - [Commits](uuidjs/uuid@v9.0.1...v14.0.0) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `turbo` from 2.2.3 to 2.9.14 - [Release notes](https://github.com/vercel/turborepo/releases) - [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md) - [Commits](vercel/turborepo@v2.2.3...v2.9.14) Updates `uuid` from 9.0.1 to 14.0.0 - [Release notes](https://github.com/uuidjs/uuid/releases) - [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md) - [Commits](uuidjs/uuid@v9.0.1...v14.0.0) Updates `uuid` from 9.0.1 to 14.0.0 - [Release notes](https://github.com/uuidjs/uuid/releases) - [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md) - [Commits](uuidjs/uuid@v9.0.1...v14.0.0) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `turbo` from 2.2.3 to 2.9.14 - [Release notes](https://github.com/vercel/turborepo/releases) - [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md) - [Commits](vercel/turborepo@v2.2.3...v2.9.14) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `next` from 15.5.15 to 15.5.18 - [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.5.15...v15.5.18) Updates `uuid` from 9.0.1 to 14.0.0 - [Release notes](https://github.com/uuidjs/uuid/releases) - [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md) - [Commits](uuidjs/uuid@v9.0.1...v14.0.0) Updates `uuid` from 9.0.1 to 14.0.0 - [Release notes](https://github.com/uuidjs/uuid/releases) - [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md) - [Commits](uuidjs/uuid@v9.0.1...v14.0.0) Updates `uuid` from 9.0.1 to 14.0.0 - [Release notes](https://github.com/uuidjs/uuid/releases) - [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md) - [Commits](uuidjs/uuid@v9.0.1...v14.0.0) Updates `uuid` from 9.0.1 to 14.0.0 - [Release notes](https://github.com/uuidjs/uuid/releases) - [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md) - [Commits](uuidjs/uuid@v9.0.1...v14.0.0) Updates `uuid` from 9.0.1 to 14.0.0 - [Release notes](https://github.com/uuidjs/uuid/releases) - [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md) - [Commits](uuidjs/uuid@v9.0.1...v14.0.0) --- updated-dependencies: - dependency-name: next dependency-version: 15.5.18 dependency-type: direct:production - dependency-name: next dependency-version: 15.5.18 dependency-type: direct:production - dependency-name: next dependency-version: 15.5.18 dependency-type: direct:production - dependency-name: next dependency-version: 15.5.18 dependency-type: direct:production - dependency-name: turbo dependency-version: 2.9.14 dependency-type: direct:development - dependency-name: uuid dependency-version: 14.0.0 dependency-type: direct:production - dependency-name: uuid dependency-version: 14.0.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/npm_and_yarn-8c89b0c7e3
branch
from
209f5eb to
0a193a0
Compare
Contributor
Prompt To Fix All With AIFix the following 3 code review issues. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 3
pnpm-lock.yaml:452-455
**Lockfile specifier mismatch for multiple packages**
The `specifier` field in `pnpm-lock.yaml` must match the exact constraint in `package.json`. After this PR, multiple packages have stale specifiers:
- `apps/auth/nextjs-ssr`: lockfile still says `specifier: 15.5.15`, but `package.json` was bumped to `"15.5.18"`
- `apps/payments/nextjs`: same mismatch
- `apps/wallets/quickstart-devkit`: same mismatch
- `apps/wallets/react`: lockfile says `specifier: 15.5.15`, but `package.json` now says `"^15.5.18"`
Any CI step using `pnpm install --frozen-lockfile` (or `pnpm ci`) will fail with an "outdated lockfile" error because the specifiers no longer match the manifests. The lockfile needs to be regenerated with `pnpm install` after these `package.json` changes.
### Issue 2 of 3
apps/wallets/react/package.json:16
**Next.js downgraded from v16 to v15 in this workspace**
The `pnpm-lock.yaml` shows that `apps/wallets/react` was previously resolving `next@16.2.3` (from specifier `^16.2.3`). This PR changes the constraint to `^15.5.18`, which is a major version downgrade. If any Next.js 16 APIs or features are used in this app, they would break silently at runtime. Please confirm this is intentional and that the app has been tested against Next.js 15.
### Issue 3 of 3
packages/client/base/package.json:27
**Large `uuid` major version jump with several breaking changes**
This bumps `uuid` from `9.0.1` to `14.0.0`, spanning five major releases. Key breaking changes across the skipped versions:
- **v12**: CommonJS support was removed — the package is now ESM-only. Any consumer using `require('uuid')` or a bundler configured for CJS will break.
- **v13**: Browser exports became the default, which changes module resolution for Node.js consumers unless they explicitly use the `node` condition.
- **v14**: Node.js ≥20 is now required; `crypto` must be globally available. If the project or its consumers run on Node 18, `uuid` will throw at runtime.
No direct `import ... from 'uuid'` was found in `packages/client/base/src`, so the impact may be limited — but please verify whether any downstream consumer of this package imports `uuid` via CommonJS or runs on Node 18.
Reviews (2): Last reviewed commit: "chore(deps): bump the npm_and_yarn group..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Comment on lines
452
to
+455
| specifier: ^14.6.1 | ||
| version: 14.6.1 | ||
| next: | ||
| specifier: ^16.2.3 | ||
| version: 16.2.3(@babel/core@7.28.5)(@playwright/test@1.54.2)(babel-plugin-macros@3.1.0)(babel-plugin-react-compiler@1.0.0)(react-dom@19.1.1(react@19.1.1))(react@19.1.1) | ||
| specifier: 15.5.15 |
Contributor
There was a problem hiding this comment.
The specifier field in pnpm-lock.yaml must match the exact constraint in package.json. After this PR, multiple packages have stale specifiers:
apps/auth/nextjs-ssr: lockfile still saysspecifier: 15.5.15, butpackage.jsonwas bumped to"15.5.18"apps/payments/nextjs: same mismatchapps/wallets/quickstart-devkit: same mismatchapps/wallets/react: lockfile saysspecifier: 15.5.15, butpackage.jsonnow says"^15.5.18"
Any CI step using pnpm install --frozen-lockfile (or pnpm ci) will fail with an "outdated lockfile" error because the specifiers no longer match the manifests. The lockfile needs to be regenerated with pnpm install after these package.json changes.
Prompt To Fix With AI
This is a comment left during a code review.
Path: pnpm-lock.yaml
Line: 452-455
Comment:
**Lockfile specifier mismatch for multiple packages**
The `specifier` field in `pnpm-lock.yaml` must match the exact constraint in `package.json`. After this PR, multiple packages have stale specifiers:
- `apps/auth/nextjs-ssr`: lockfile still says `specifier: 15.5.15`, but `package.json` was bumped to `"15.5.18"`
- `apps/payments/nextjs`: same mismatch
- `apps/wallets/quickstart-devkit`: same mismatch
- `apps/wallets/react`: lockfile says `specifier: 15.5.15`, but `package.json` now says `"^15.5.18"`
Any CI step using `pnpm install --frozen-lockfile` (or `pnpm ci`) will fail with an "outdated lockfile" error because the specifiers no longer match the manifests. The lockfile needs to be regenerated with `pnpm install` after these `package.json` changes.
How can I resolve this? If you propose a fix, please make it concise.| "@solana/web3.js": "1.98.1", | ||
| "@stellar/stellar-sdk": "^14.6.1", | ||
| "next": "^16.2.3", | ||
| "next": "^15.5.18", |
Contributor
There was a problem hiding this comment.
The pnpm-lock.yaml shows that apps/wallets/react was previously resolving next@16.2.3 (from specifier ^16.2.3). This PR changes the constraint to ^15.5.18, which is a major version downgrade. If any Next.js 16 APIs or features are used in this app, they would break silently at runtime. Please confirm this is intentional and that the app has been tested against Next.js 15.
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/wallets/react/package.json
Line: 16
Comment:
**Next.js downgraded from v16 to v15 in this workspace**
The `pnpm-lock.yaml` shows that `apps/wallets/react` was previously resolving `next@16.2.3` (from specifier `^16.2.3`). This PR changes the constraint to `^15.5.18`, which is a major version downgrade. If any Next.js 16 APIs or features are used in this app, they would break silently at runtime. Please confirm this is intentional and that the app has been tested against Next.js 15.
How can I resolve this? If you propose a fix, please make it concise.| "@datadog/browser-logs": "6.24.1", | ||
| "exponential-backoff": "3.1.1", | ||
| "uuid": "9.0.1", | ||
| "uuid": "14.0.0", |
Contributor
There was a problem hiding this comment.
uuid major version jump with several breaking changes
This bumps uuid from 9.0.1 to 14.0.0, spanning five major releases. Key breaking changes across the skipped versions:
- v12: CommonJS support was removed — the package is now ESM-only. Any consumer using
require('uuid')or a bundler configured for CJS will break. - v13: Browser exports became the default, which changes module resolution for Node.js consumers unless they explicitly use the
nodecondition. - v14: Node.js ≥20 is now required;
cryptomust be globally available. If the project or its consumers run on Node 18,uuidwill throw at runtime.
No direct import ... from 'uuid' was found in packages/client/base/src, so the impact may be limited — but please verify whether any downstream consumer of this package imports uuid via CommonJS or runs on Node 18.
Prompt To Fix With AI
This is a comment left during a code review.
Path: packages/client/base/package.json
Line: 27
Comment:
**Large `uuid` major version jump with several breaking changes**
This bumps `uuid` from `9.0.1` to `14.0.0`, spanning five major releases. Key breaking changes across the skipped versions:
- **v12**: CommonJS support was removed — the package is now ESM-only. Any consumer using `require('uuid')` or a bundler configured for CJS will break.
- **v13**: Browser exports became the default, which changes module resolution for Node.js consumers unless they explicitly use the `node` condition.
- **v14**: Node.js ≥20 is now required; `crypto` must be globally available. If the project or its consumers run on Node 18, `uuid` will throw at runtime.
No direct `import ... from 'uuid'` was found in `packages/client/base/src`, so the impact may be limited — but please verify whether any downstream consumer of this package imports `uuid` via CommonJS or runs on Node 18.
How can I resolve this? If you propose a fix, please make it concise.
Contributor
Author
|
Superseded by #1875. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/npm_and_yarn-8c89b0c7e3
branch
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.
Bumps the npm_and_yarn group with 3 updates in the / directory: turbo, next and uuid.
Bumps the npm_and_yarn group with 1 update in the /apps/auth/nextjs-ssr directory: next.
Bumps the npm_and_yarn group with 1 update in the /apps/payments/nextjs directory: next.
Bumps the npm_and_yarn group with 1 update in the /apps/wallets/quickstart-devkit directory: next.
Bumps the npm_and_yarn group with 1 update in the /packages/client/base directory: uuid.
Updates
turbofrom 2.2.3 to 2.9.14Release notes
Sourced from turbo's releases.
... (truncated)
Commits
fc62fe0publish 2.9.14 to registryfb8c9aechore: Release 2.9.13 (#12803)e8e629dfix: Avoid project-local Yarn during detection (#12801)91c90cbfix: Harden VS Code extension command execution (#12800)84f4508fix: Validate auth callback state (#12802)1779ad7Removed unneeded import form hash creation script in docs (#12799)71f8c90test: Validate lockfiles without dependency downloads (#12789)5fcb960ci: Scope GitHub Actions caches by branch (#12788)4cf9fabci: Usepull_requestfor PR title linting (#12787)859c629fix: Restore docs mobile menu (#12782)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for turbo since your current version.
Updates
nextfrom 15.5.15 to 15.5.18Release notes
Sourced from next's releases.
Commits
9ff92cev15.5.1800ebe23[backport] Disable build caches for production/staging/force-preview deploys ...62c97abv15.5.17423623aTurbopack: Match proxy matchers with webpack implementation (#93594)fa78739Turbopack: Fix middleware matcher suffix (#93590)36e62c6[backport] Turbopack: more strict vergen setup (#93588)36589b5[backport][test] Pin package manager to patch versions (#93596)ad6fd4ev15.5.1679d7dffIgnore malformed CSP nonce headers (#103)c4f6908router-server: guard upgrade proxy against absolute-url SSRF (#77) (#102)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for next since your current version.
Updates
uuidfrom 9.0.1 to 14.0.0Release notes
Sourced from uuid's releases.
... (truncated)
Changelog
Sourced from uuid's changelog.
... (truncated)
Commits
7c1ea08chore(main): release 14.0.0 (#926)3d2c5b0Merge commit from forkf2c235ffix!: expectcryptoto be global everywhere (requires node@20+) (#935)529ef08chore: upgrade TypeScript and fixup types (#927)086fd79chore: update dependencies (#933)dc4ddb8feat!: drop node@18 support (#934)0f1f9c9chore: switch to Biome for parsing and linting (#932)e2879e6chore: use maintained version of npm-run-all (#930)ffa3138fix: Use GITHUB_TOKEN for release-please and enable npm provenance (#925)0423d49docs: remove obsolete v1 option notes (#915)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for uuid since your current version.
Install script changes
This version adds
preparescript that runs during installation. Review the package contents before updating.Updates
nextfrom 15.5.15 to 15.5.18Release notes
Sourced from next's releases.
Commits
9ff92cev15.5.1800ebe23[backport] Disable build caches for production/staging/force-preview deploys ...62c97abv15.5.17423623aTurbopack: Match proxy matchers with webpack implementation (#93594)fa78739Turbopack: Fix middleware matcher suffix (#93590)36e62c6[backport] Turbopack: more strict vergen setup (#93588)36589b5[backport][test] Pin package manager to patch versions (#93596)ad6fd4ev15.5.1679d7dffIgnore malformed CSP nonce headers (#103)c4f6908router-server: guard upgrade proxy against absolute-url SSRF (#77) (#102)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for next since your current version.
Updates
turbofrom 2.2.3 to 2.9.14Release notes
Sourced from turbo's releases.
... (truncated)
Commits
fc62fe0publish 2.9.14 to registryfb8c9aechore: Release 2.9.13 (#12803)e8e629dfix: Avoid project-local Yarn during detection (#12801)91c90cbfix: Harden VS Code extension command execution (#12800)84f4508fix: Validate auth callback state (#12802)1779ad7Removed unneeded import form hash creation script in docs (#12799)71f8c90test: Validate lockfiles without dependency downloads (#12789)5fcb960ci: Scope GitHub Actions caches by branch (#12788)4cf9fabci: Usepull_requestfor PR title linting (#12787)859c629fix: Restore docs mobile menu (#12782)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for turbo since your current version.
Updates
uuidfrom 9.0.1 to 14.0.0Release notes
Sourced from uuid's releases.
... (truncated)
Changelog
Sourced from uuid's changelog.
... (truncated)
Commits
7c1ea08chore(main): release 14.0.0 (#926)3d2c5b0Merge commit from forkf2c235ffix!: expectcryptoto be global everywhere (requires node@20+) (#935)529ef08chore: upgrade TypeScript and fixup types (#927)086fd79chore: update dependencies (#933)dc4ddb8feat!: drop node@18 support (#934)0f1f9c9chore: switch to Biome for parsing and linting (#932)e2879e6chore: use maintained version of npm-run-all (#930)ffa3138fix: Use GITHUB_TOKEN for release-please and enable npm provenance (#925)0423d49docs: remove obsolete v1 option notes (#915)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for uuid since your current version.
Install script changes
This version adds
preparescript that runs during installation. Review the package contents before updating.Updates
nextfrom 15.5.15 to 15.5.18Release notes
Sourced from next's releases.
Commits
9ff92cev15.5.1800ebe23[backport] Disable build caches for production/staging/force-preview deploys ...62c97abv15.5.17423623aTurbopack: Match proxy matchers with webpack implementation (#93594)fa78739Turbopack: Fix middleware matcher suffix (#93590)36e62c6[backport] Turbopack: more strict vergen setup (#93588)36589b5[backport][test] Pin package manager to patch versions (#93596)ad6fd4ev15.5.1679d7dffIgnore malformed CSP nonce headers (#103)c4f6908router-server: guard upgrade proxy against absolute-url SSRF (#77) (#102)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for next since your current version.
Updates
turbofrom 2.2.3 to 2.9.14Release notes
Sourced from turbo's releases.