Repository navigation
Tag the built core library on git - #34
Merged
Merged
Conversation
npm cannot install a package from a folder of a git repository, and dist is not committed. A workflow now packs packages/core after CI passes on main and pushes the packed files as the tag core-v<version>, so that npm install git+https://...#core-v<version> works without npm. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
After CI passes on main, a workflow packs
packages/coreand pushes the packed files as the tagcore-v<version>. npm can then install the library from git without npm publishing:It can also be run by hand (Actions → Core on git → Run workflow) for an existing tag such as
v0.5.0. The core README's Install section now says this.🤖 Generated with Claude Code