Skip to content

chore: bump @posthog/cli to 0.16.2 - #4737

Merged
cat-ph merged 1 commit into
mainfrom
cat/bump-cli-0.16.2
Sep 2, 2026
Merged

chore: bump @posthog/cli to 0.16.2#4737
cat-ph merged 1 commit into
mainfrom
cat/bump-cli-0.16.2

Conversation

@cat-ph

@cat-ph cat-ph commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Problem

On Next.js 16.3+, next build with withPostHogConfig can abort with Chunk ID not found (#4667). Turbopack's filesystem cache keeps writing into distDir while @posthog/nextjs-config runs posthog-cli sourcemap process, and CLI versions up to 0.16.1 walked the directory once for inject and again for upload, so a chunk that appeared between the two walks reached upload unstamped and failed the build.

The root fix landed in the CLI (PostHog/posthog#91427, released as @posthog/cli 0.16.2): process now uploads exactly the pairs it injected. The build plugins still pin the CLI to ~0.14.1, so users do not get it until the catalog moves.

Changes

  • Bump the shared @posthog/cli catalog range to ~0.16.2 and regenerate the root lockfile.
  • Patch changesets for the four packages that publish the CLI dependency: @posthog/nextjs-config, @posthog/nuxt, @posthog/rollup-plugin, @posthog/webpack-plugin.

No code changes. CLI 0.15.x and 0.16.x add Info.plist release metadata and Hermes --release-mode; nothing the plugins invoke changed shape. Supersedes #4681, which worked around the race on the JS side by snapshotting distDir into a stdin file list.

Independent example and playground lockfiles still resolve 0.11.1 and are left alone, as in #4563.

How did you test this code?

pnpm install --frozen-lockfile --lockfile-only passes on the regenerated lockfile. No unit tests run: dependency-only change, CI covers the plugin packages.

Release info Sub-libraries affected

Libraries affected

  • @posthog/nextjs-config
  • @posthog/nuxt
  • @posthog/rollup-plugin
  • @posthog/webpack-plugin

Checklist

  • Tests for new code
  • Accounted for the impact of any changes across different platforms
  • Accounted for backwards compatibility of any changes (no breaking changes!)
  • Took care not to unnecessarily increase the bundle size

If releasing new changes

  • Ran pnpm changeset to generate a changeset file

@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor
⚠️ Possible changeset mismatch — 4 extra

This is informational — the PR is not blocked. Click the triangle above to collapse, or push a fix and this comment will auto-delete.

Declared in a changeset but no source files modified:

  • @posthog/nextjs-config
  • @posthog/nuxt
  • @posthog/rollup-plugin
  • @posthog/webpack-plugin

Double-check this is intentional — for example, releasing a previously-merged change.

Changesets in this PR:

  • @posthog/nextjs-config — patch
  • @posthog/nuxt — patch
  • @posthog/rollup-plugin — patch
  • @posthog/webpack-plugin — patch

@cat-ph
cat-ph marked this pull request as ready for review September 1, 2026 23:48
@cat-ph
cat-ph requested a review from a team as a code owner September 1, 2026 23:48
@cat-ph
cat-ph requested review from a team, ablaszkiewicz and hpouillot September 1, 2026 23:48
@greptile-apps

greptile-apps Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Reviews (1): Last reviewed commit: "chore: bump @posthog/cli to 0.16.2" | Re-trigger Greptile

@cat-ph
cat-ph merged commit c589ab8 into main Sep 2, 2026
66 checks passed
@cat-ph
cat-ph deleted the cat/bump-cli-0.16.2 branch September 2, 2026 10:54
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