fix(release): refresh lockfile for 1.2.0 publish#12
Merged
Conversation
…te the lockfile The changeset version bump set internal deps to ^1.2.0 in package.json but left pnpm-lock.yaml at ^1.1.0, so the Release job's frozen-lockfile install failed before publishing. Regenerate the lockfile and make the version-packages script run 'pnpm install --lockfile-only' so future Version Packages PRs stay in sync. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ApprovabilityVerdict: Needs human review Unable to check for correctness in e85535d. You can customize Macroscope's approvability policy. Learn more. |
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
1 participant
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 Version Packages merge (#11) bumped internal deps to
^1.2.0inpackage.jsonbutchangeset versiondid not refreshpnpm-lock.yaml(still^1.1.0). The Release job runspnpm install --frozen-lockfile, which then fails withERR_PNPM_OUTDATED_LOCKFILE— so 1.2.0 never published (npm still on 1.1.0).Fix
pnpm-lock.yamlto match the^1.2.0specs (verifiedpnpm install --frozen-lockfilenow passes).version-packagesrunpnpm install --lockfile-onlyafterchangeset version, so future Version Packages PRs keep the lockfile in sync and this can't recur.Merging this re-triggers the Release workflow, which (no pending changesets) runs
changeset publishand ships core/cli 1.2.0 + templates 1.1.1.🤖 Generated with Claude Code
Note
Refresh pnpm lockfile automatically during version-packages releases
Updates the
version-packagesnpm script in package.json to appendpnpm install --lockfile-onlyafterchangeset version, keepingpnpm-lock.yamlin sync without installing packages. This fixes the stale lockfile that was present for the 1.2.0 publish.Macroscope summarized e85535d.