Conversation
Updated package.json files across multiple applications and packages to replace caret (^) versioning with exact versions for dependencies and devDependencies, ensuring consistent installations. This includes updates for arktype, tsx, and various other packages.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughThis PR converts caret (^) SemVer ranges to exact version pins across many package.json files in apps, packages, tooling, and the repo root, altering dependency and devDependency entries only (no code or exported API changes). Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Notes for reviewers:
Possibly related PRs
Suggested labels
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (4)
🚧 Files skipped from review as they are similar to previous changes (2)
🧰 Additional context used🧠 Learnings (1)📚 Learning: 2025-09-09T17:37:19.650ZApplied to files:
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
🔇 Additional comments (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
bot
added
arkenv
…ock.yaml Updated pnpm-lock.yaml to replace caret (^) versioning with exact versions for various dependencies and devDependencies, ensuring consistent installations across applications. This includes updates for packages like arktype, tsx, and others.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (7)
apps/playgrounds/node/package.json(1 hunks)apps/playgrounds/vite/package.json(1 hunks)apps/www/package.json(1 hunks)package.json(1 hunks)packages/arkenv/package.json(1 hunks)packages/vite-plugin/package.json(1 hunks)tooling/playwright-www/package.json(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2025-09-10T19:35:18.179Z
Learnt from: yamcodes
Repo: yamcodes/arkenv PR: 136
File: .changeset/vast-bananas-win.md:2-3
Timestamp: 2025-09-10T19:35:18.179Z
Learning: The arkenv package is currently in v0.x.x (pre-1.0) development phase, where breaking changes are acceptable in minor version bumps according to semantic versioning conventions.
Applied to files:
packages/arkenv/package.json
📚 Learning: 2025-09-09T17:37:19.650Z
Learnt from: yamcodes
Repo: yamcodes/arkenv PR: 132
File: packages/arkenv/README.md:13-14
Timestamp: 2025-09-09T17:37:19.650Z
Learning: For yamcodes/arkenv project: Runtime support documentation should link to specific examples: Node.js (examples/basic), Bun (examples/with-bun), Vite (examples/with-vite-react-ts).
Applied to files:
packages/arkenv/package.jsonapps/playgrounds/vite/package.json
🔇 Additional comments (6)
apps/playgrounds/node/package.json (1)
12-12: Pinning strategy looks correct for this app.All dependencies and devDependencies are pinned to exact versions, consistent with the PR objectives for apps.
Also applies to: 16-16
packages/arkenv/package.json (1)
43-51: Pinning strategy is correct for a Node.js-only library.DevDependencies are pinned to exact versions while peerDependencies maintain semver ranges, enabling dev environment consistency without restricting consumers.
package.json (1)
28-38: Partial version pinning at root level—verify intentionality.The root package.json pins
typescriptandvitest(lines 36–37) but keeps caret ranges for other devDependencies (lines 29–35). This inconsistency with the PR's stated goal of "pin package versions for better reliability and predictability" warrants verification. If selective pinning is intentional, consider documenting the rationale; otherwise, align with the pinning strategy across the monorepo.packages/vite-plugin/package.json (1)
14-20: Pinning strategy is correct for a dual browser/node library.DevDependencies are pinned to exact versions for development consistency, while peerDependencies maintain semantic version ranges for consumer flexibility. No regular dependencies to coordinate.
apps/www/package.json (1)
16-47: Comprehensive pinning is correct for this app.All dependencies (lines 16–47) and devDependencies (lines 50–70) are pinned to exact versions, providing the "certainty about installed versions" and "reliability and predictability" goals stated in the PR objectives.
Also applies to: 50-70
apps/playgrounds/vite/package.json (1)
27-27: App dependencyviteuses unpinned@latesttag—inconsistent with other pinned dependencies.The observation is factually correct: line 27 specifies
vite: "npm:rolldown-vite@latest"while every other dependency in this file is pinned to an exact version (e.g.,"5.1.0","19.2.0"). This is also the only@latestreference across all app playgrounds.However, without access to the PR description, I cannot confirm whether this violates the stated pinning requirements. Please verify:
- Whether the PR explicitly mandates pinning all dependencies in apps
- Whether rolldown-vite's
@latestis intentional (e.g., testing upcoming versions) or an oversightIf pinning is required, change to
"npm:rolldown-vite@X.Y.Z"with a specific version. If it's intentional, document the exception.
…stency Updated package.json and lock files across multiple applications to replace caret (^) versioning with exact versions for dependencies and devDependencies, ensuring consistent installations. This includes updates for packages like react, typescript, and others.
github-actions
bot
added
the
github actions
commit: |
📦 Bundle Size Report✅ All size limits passed! |
yamcodes
deleted the
306-pin-package-versions-for-better-reliability-and-predictability
branch
1 participant
Updated package.json files across multiple applications and packages to replace caret (^) versioning with exact versions for dependencies and devDependencies, ensuring consistent installations. This includes updates for arktype, tsx, and various other packages.
Closes #306
Summary by CodeRabbit