Skip to content

chore: bump pnpm to 11.1.2 - #204

Merged
cpojer merged 1 commit into
mainfrom
chore/bump-pnpm-11.1.2
May 18, 2026
Merged

cpojer merged 1 commit into
mainfrom
chore/bump-pnpm-11.1.2

Conversation

@Boshen

@Boshen Boshen commented May 17, 2026

Copy link
Copy Markdown
Member

Bumps the repo-root packageManager pin to pnpm@11.1.2.

Only the root package.json packageManager field is changed.

@netlify

netlify Bot commented May 17, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for staging-void-cloud ready!

Name Link
🔨 Latest commit e6dc5ec
🔍 Latest deploy log https://app.netlify.com/projects/staging-void-cloud/deploys/6a09dbfa61c1d20008e6ba64
😎 Deploy Preview https://deploy-preview-204--staging-void-cloud.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@cpojer
cpojer merged commit 34d36ca into main May 18, 2026
9 checks passed
@cpojer
cpojer deleted the chore/bump-pnpm-11.1.2 branch May 18, 2026 03:21
cpojer pushed a commit that referenced this pull request Sep 11, 2026
…204)

#200 (Renovate) bumped catalog hono 4.12.18 -> 4.12.27, diverging from the
framework submodule (framework/packages/void pins ^4.12.18). The dashboard
typechecks against the framework's void/@void runtime types (built on hono
4.12.18), so the newer Context<…> generics broke `vp run check`:

  packages/dashboard/middleware/01.auth.ts        TS2769 / TS2345
  packages/dashboard/pages/auth/callback.server.ts TS2345
  Context<CloudEnv,…> not assignable to Context<any,any,{}>

main has been red since #200 (2026-06-28); the Deploy-Staging gate stays
skipped while lint-and-check is red. Pin the catalog back to 4.12.18 to
restore the known-good pairing.

Verified: vp run check / vp lint / vp fmt --check all pass.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
cpojer pushed a commit that referenced this pull request Sep 11, 2026
)

The lint-and-check CI job failed at `vp run check`: the platform root
resolved hono@4.12.27 while the framework submodule pins ^4.12.18, so the
dashboard's CloudContext (typed against 4.12.18) was no longer assignable
to the platform's 4.12.27 Context (TS2345 — 4.12.27's HonoRequest adds
`bytes`/`[GET_MATCH_RESULT]`).

This is a recurring renovate regression: #200 first bumped it, #204
pinned it back with a warning comment, and #218 bumped it again past the
comment. Comments don't stop renovate, so:

- re-pin catalog hono to 4.12.18 (lockstep with the submodule) + lockfile
- disable renovate for hono in .github/renovate.json — it's now manually
  managed to track the framework submodule's hono

Verified locally: `vp run check`, `vp lint`, `vp fmt --check` all pass.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

2 participants