Skip to content

chore(deps): update pnpm to v12 - #45

Merged
codeSTACKr merged 3 commits into
mainfrom
chore/pnpm-12
Nov 13, 2026
Merged

codeSTACKr merged 3 commits into
mainfrom
chore/pnpm-12

Conversation

@codeSTACKr

Copy link
Copy Markdown
Contributor

What

  • packageManager: pnpm@12.18.0 in root and frontend/package.json; the agent-ts template workflow pins 12.18.0 too. The agent-ts Dockerfile installs pnpm 12 and copies pnpm-workspace.yaml.
  • Every lockfile (root, frontend, agent-ts, db) regenerated with pnpm 12, so resolution respects its 1-day minimumReleaseAge (the policy is not relaxed).
  • pnpm-workspace.yaml with allowBuilds in root, agent-ts and db, for dependencies with install scripts (pnpm 11+ fails installs on unreviewed build scripts). These packages ship prebuilt binaries, so their scripts stay disabled, as they were under pnpm 10.
  • renovate.json: top-level "minimumReleaseAge": "1 day" so Renovate never proposes versions pnpm would reject.

Supersedes #27, which was based on an older main and kept the old lockfiles.

How tested

See the validation comment below.

🤖 Generated with Claude Code

https://claude.ai/code/session_013EcAtRg8aYia9VZrTAZ4Av

codeSTACKr and others added 3 commits November 13, 2026 16:28
- packageManager pnpm@12.18.0 (root, frontend) and the agent-ts template
  workflow; agent-ts Dockerfile installs pnpm 12 and copies
  pnpm-workspace.yaml.
- Regenerate every lockfile with pnpm 12 so resolution respects its
  1-day minimumReleaseAge.
- pnpm-workspace.yaml allowBuilds where dependencies have install
  scripts (pnpm 11+ fails installs on unreviewed build scripts).
- Renovate: minimumReleaseAge "1 day" so it never proposes versions
  pnpm would reject.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013EcAtRg8aYia9VZrTAZ4Av
- packageManager pnpm@12.18.0 (root, frontend) and the agent-ts template
  workflow; agent-ts Dockerfile installs pnpm 12 and copies
  pnpm-workspace.yaml.
- Regenerate every lockfile with pnpm 12 so resolution respects its
  1-day minimumReleaseAge.
- pnpm-workspace.yaml allowBuilds where dependencies have install
  scripts (pnpm 11+ fails installs on unreviewed build scripts).
- Renovate: minimumReleaseAge "1 day" so it never proposes versions
  pnpm would reject.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013EcAtRg8aYia9VZrTAZ4Av
- agent-ts: allowBuilds entries (all disabled, as under pnpm 10) for
  packages with install scripts; add @livekit/rtc-node, now a required
  peer of @livekit/agents 1.9.
- frontend: import RoomConfiguration/RoomAgentDispatch from
  livekit-server-sdk and drop the direct @livekit/protocol dependency,
  which resolved to a different version than the SDK's pinned one;
  type motion's ease as a literal.
- Reformat with prettier 3.10.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013EcAtRg8aYia9VZrTAZ4Av
@codeSTACKr

Copy link
Copy Markdown
Contributor Author

Validated: CI green (frontend lint/typecheck/format/build, agent-ts lint/typecheck/format/test/build, agent-py, deno check, both Docker images). Locally with pnpm 12.18.0: pnpm install --frozen-lockfile passes in root, frontend, agent-ts and db; agent-ts lint/typecheck/format check/tests/build and --help pass; db typecheck passes; frontend lint (warnings only, same as main)/typecheck/format check pass; next build + smoke test on next start match main (/ 200, /opengraph-image 200 with an identical image size, POST /api/token 500 without LiveKit keys, the proxy attempts to refresh an expired session cookie). The regenerated lockfiles picked up newer versions, which needed the follow-up fixes in the second commit (rtc-node peer, protocol import, motion ease typing, prettier 3.10 formatting).

@codeSTACKr
codeSTACKr merged commit 1cb0fb7 into main Nov 13, 2026
10 checks passed
@codeSTACKr
codeSTACKr deleted the chore/pnpm-12 branch November 13, 2026 18:20
@codeSTACKr codeSTACKr mentioned this pull request Nov 13, 2026
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant