chore: bump @posthog/cli to 0.16.2 - #4737
Merged
Merged
Conversation
6 tasks
Contributor
|
Contributor
|
Reviews (1): Last reviewed commit: "chore: bump @posthog/cli to 0.16.2" | Re-trigger Greptile |
turnipdabeets
approved these changes
Sep 1, 2026
12 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
On Next.js 16.3+,
next buildwithwithPostHogConfigcan abort withChunk ID not found(#4667). Turbopack's filesystem cache keeps writing intodistDirwhile@posthog/nextjs-configrunsposthog-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/cli0.16.2):processnow 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
@posthog/clicatalog range to~0.16.2and regenerate the root lockfile.@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 snapshottingdistDirinto 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-onlypasses on the regenerated lockfile. No unit tests run: dependency-only change, CI covers the plugin packages.Release info Sub-libraries affected
Libraries affected
Checklist
If releasing new changes
pnpm changesetto generate a changeset file