chore(deps): regenerate pnpm-lock.yaml after ep_plugin_helpers bump#144
Merged
Conversation
Prior package.json bump (commit `b33bcce`) left the lockfile pinned to ^0.5.x while the manifest moved to ^0.6.x. The release workflow's `pnpm i --frozen-lockfile` step has been failing ever since, blocking every npm publish — fresh installs still resolve ep_plugin_helpers@0.5.3 even though main has ^0.6.x. Regenerate the lockfile so the next push to the default branch can re-publish cleanly. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
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.
Why
The earlier bump of
ep_plugin_helpersto^0.6.1inpackage.jsonwas not accompanied by apnpm-lock.yamlupdate. The release workflow (.github/workflows/npmpublish.yml) runspnpm i --frozen-lockfilebefore the version bump, which fails withERR_PNPM_OUTDATED_LOCKFILE. As a result no publish has run since that change landed, and fresh installs of this plugin still resolveep_plugin_helpers@0.5.3from npm rather than the current0.6.xline — which means consumers miss ether/ep_plugin_helpers#19's correction of the misleading "Etherpad < 2.7.4" degradation warning.What
pnpm installso the lockfile picks up the new manifest range.Merging this PR triggers the release workflow on the next push to the default branch, which should now publish a fresh patch release.
🤖 Generated with Claude Code