fix(ci): use --no-frozen-lockfile in posthog-upgrade workflow#3124
Merged
marandaneto merged 1 commit intomainfrom Feb 20, 2026
Merged
fix(ci): use --no-frozen-lockfile in posthog-upgrade workflow#3124marandaneto merged 1 commit intomainfrom
marandaneto merged 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📝 No Changeset FoundThis PR doesn't include a changeset. A changeset (and the release label) is required to release a new version. How to add a changesetRun this command and follow the prompts: pnpm changesetRemember: Never use |
veryayskiy
approved these changes
Feb 20, 2026
Member
Author
|
https://github.com/PostHog/posthog-js/actions/workflows/posthog-upgrade.yml broken for a while |
Contributor
Contributor
|
Size Change: 0 B Total Size: 6.17 MB ℹ️ View Unchanged
|
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
The
posthog-upgrade.ymlworkflow is failing with:After
tazeupdates the posthog-js version in the pnpm catalog (pnpm-workspace.yaml),pnpm irefuses to proceed because frozen-lockfile mode is enabled and the catalog no longer matches the lockfile.Fix
Use
pnpm i --no-frozen-lockfilesince the whole purpose of this step is to update the dependency and regenerate the lockfile.