chore: upgrade pnpm and eslint - #1750
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
More templates
@orpc/ai-sdk
@orpc/arktype
@orpc/bun
@orpc/client
@orpc/cloudflare
@orpc/contract
@orpc/experimental-effect
@orpc/evlog
@orpc/json-schema
@orpc/nest
@orpc/next
@orpc/openapi
@orpc/opentelemetry
@orpc/pinia-colada
@orpc/pino
@orpc/publisher
@orpc/ratelimit
@orpc/server
@orpc/shared
@orpc/swr
@orpc/tanstack-query
@orpc/trpc
@orpc/valibot
@orpc/zod
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Merging this PR will improve performance by 10.59%
|
| Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|
| ⚡ | octet stream |
916.4 µs | 828.6 µs | +10.59% |
Tip
Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.
Comparing dinwwwh:chore/upgrade-pnpm-and-eslint (0ce0284) with main (8521593)1
Footnotes
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
packageManagerfrompnpm@11.10.0topnpm@11.17.0: triggers lockfile resolution metadata regeneration —supports-color@10.2.2is threaded through transitive dependency entries as pnpm now tracks it pervasively.@antfu/eslint-configspecifier^9.0.0→^9.2.0andeslintspecifier^10.5.0→^10.8.0: no actual version changes — both were already resolved to the bumped versions (9.2.0 and 10.8.0 respectively). Lockfile entries update only their specifier lines and addsupports-color@10.2.2to resolution metadata.pkg-pr-new^0.0.79→^0.0.82: only actual resolved version bump in this PR (dev dependency for CI preview publishing).
DeepSeek Pro (free via Pullfrog for OSS) | 𝕏

No description provided.