Skip to content

The repository installs and checks with pnpm 12.7.0 and still publishes with npm - #3

Merged
bowendeng merged 7 commits into
mainfrom
chore/pnpm
Oct 11, 2026
Merged

bowendeng merged 7 commits into
mainfrom
chore/pnpm

Conversation

@bowendeng

Copy link
Copy Markdown
Contributor

Moves the packages from npm to pnpm. Draft: it runs the required check on GitHub and is not to be merged until the maintainer decides. The release workflow keeps its file name, job name, trigger and permissions, and still publishes with npm publish.

…release that is two weeks old, with the same resolved versions except acorn, ignore and prettier, which fall back to the newest that is two weeks old, and with minimumReleaseAge set to 14 days
…exec, which finds them in the project like npx --no-install did
…ments check refuses a private script written as pnpm run as it did as npm run
…ion-setup before setup-node, cache and install with pnpm and run the check with pnpm, while the release still installs npm 11.21.0 and publishes with npm publish under the same file name, job name, trigger and permissions
…cking and preparing a release, and say why the release still publishes with npm publish under the file name that npmjs.com trusts
… lists pnpm 7 to 10 and not the pnpm 12 lockfile, and it ignores minimumReleaseAge, so the packages are updated by hand
…nd, with pnpm outdated and pnpm update, the 14-day rule that minimumReleaseAge enforces, and when to delete the two exclusions
@bowendeng
bowendeng marked this pull request as ready for review October 11, 2026 22:00
@bowendeng
bowendeng merged commit 06b4457 into main Oct 11, 2026
2 checks passed
@bowendeng
bowendeng deleted the chore/pnpm branch October 11, 2026 22:07
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.

1 participant