Skip to content

Bump uuid from 9.0.1 to 14.0.0 in /packages/proxy in the npm_and_yarn group across 1 directory #613

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

Closed
dependabot wants to merge 1 commit into from
Closed

Bump uuid from 9.0.1 to 14.0.0 in /packages/proxy in the npm_and_yarn group across 1 directory #613

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/proxy/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@
"jsonwebtoken": "^9.0.3",
"openai": "4.104.0",
"openapi-json-schema": "^2.0.0",
"uuid": "^9.0.1",
"uuid": "^14.0.0",
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 21, 2026

Choose a reason for hiding this comment

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

P1 Badge Update lockfile for the uuid major-version bump

After changing packages/proxy/package.json to uuid: ^14.0.0, the workspace lockfile is still pinned to uuid specifier/version ^9.0.1/9.0.1 under packages/proxy (pnpm-lock.yaml lines 263-265). This makes dependency state inconsistent and will break CI installs that use frozen lockfiles (see .github/workflows/js.yaml Install dependencies step running pnpm install --frozen-lockfile), so this dependency update is not actually consumable until the lockfile is regenerated and committed.

Useful? React with 👍 / 👎.

"zod": "^3.25.34"
}
}
Loading