chore: update dependencies and pnpm tooling - #53
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. WalkthroughThe pull request updates the project to pnpm 11.24.0 in the package manifest and CI workflow. It upgrades application and development dependencies, including Next.js, React tooling, PostHog packages, Vite, Vitest, and Vercel. It adds pnpm dependency policies for release age, build scripts, and package overrides. It also excludes selected Next.js 16.3.3 packages from release-age enforcement and grants CI read-only repository content permissions. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning These MCP integrations need to be re-authenticated in the Integrations settings: Linear Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cd5c9b7d77
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - . | ||
|
|
||
| blockExoticSubdeps: false | ||
| minimumReleaseAgeStrict: true |
There was a problem hiding this comment.
Configure the 24-hour quarantine duration
When a developer or dependency-update job resolves versions instead of replaying the frozen lockfile, minimumReleaseAgeStrict: true does not establish any quarantine by itself. The pnpm setting reference defines minimumReleaseAge—whose default is 0—as the number of minutes releases must age, so newly published packages remain immediately eligible and the exclusion list has no practical effect. Add minimumReleaseAge: 1440 to enforce the claimed 24-hour quarantine.
Useful? React with 👍 / 👎.
Summary
Validation
Cloudflare dry-run is not applicable because this repository has no Cloudflare configuration. Vercel preview is Ready; production deployment awaits the required protected-branch approval and merge.