Build system rework #106
Merged
Build system rework #106
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Jaaneek
approved these changes
May 29, 2025
… github actions for publishing
MrKampla
force-pushed
the
build-system-rework
branch
from
63e41b4 to
87790ad
Compare
Collaborator
Author
This was referenced May 29, 2025
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.
Migrate to use pkgroll, pnpm workspaces, vitest and github actions for publishing the package:
e.g. 2.1.2-canary.35.2 Thanks to this setup we won't have clashing package versions and can quickly deliver the canary version for someone who needs the fix asap.
@Jaaneek in order for the actions to work, you need to add NPM_TOKEN to repository secrets