Repository navigation
Publish each library's build to a branch, for use before npm - #5
Merged
Merged
Conversation
Until the libraries are released to npm, a passing push to main puts each built library on its own branch -- dist/<library> -- with the package at the root, which npm installs as a git dependency. Only commits whose tests passed are published, one publish at a time, and each build is a commit on top of the last. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…build From review: a manual run from another branch would have published that branch untested; checkout left the write token in .git/config while npm install scripts and the build ran; and test runs finishing out of order could publish an older build over a newer one. Manual runs are main only, the token reaches only the push step, and a commit that is no longer main's tip is not published. 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
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.
Until the libraries are released to npm, WebsiteAngular (and anyone else) installs them from GitHub.
How it works:
main, a new workflow builds the libraries.dist/ngx-reactome-cytoscape-style,dist/ngx-reactome-style,dist/ngx-reactome-diagram. The package sits at the branch root.github:reactome/ngx-reactome-base#dist/<library>. Its lockfile pins the exact build commit.This is the same pattern WebsiteAngular already uses for the cytoscape.js fork (
#svg-export-dist).Safeguards:
maincommits are published, and only for push events: a PR run never publishes.Checked:
The README says how to install from these branches.
🤖 Generated with Claude Code