chore: migrate to pnpm and setup release pipeline #62
Conversation
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
sha1n
force-pushed
the
migrate-to-pnpm
branch
3 times, most recently
from
fd2da3b to
8c90e98
Compare
- Migrated dependency management from Yarn to pnpm 10.28.0. - Updated package.json with pnpm-specific configurations and scripts. - Configured publishConfig for public NPM registry access. - Updated CI and Coverage workflows to use pnpm actions. - Added a release pipeline for automated tagging and NPM publishing via OIDC. - Integrated Release Drafter for automated release notes and draft generation. - Cleaned up legacy Yarn configuration and the invalid .npmrc file.
sha1n
force-pushed
the
migrate-to-pnpm
branch
from
8c90e98 to
35c217c
Compare
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.
No description provided.