npm public release with GitHub Actions#193
Conversation
|
|
|
Hi, I've completed the development of testing for the npm public release. The bindings are working well and i've successfully tested them with a published test package https://www.npmjs.com/package/@realtmxi/libcachesim-node?activeTab=code (support linux platform only) To enable automatic npm package publishing form the main repo, you'll need to
|
|
There was a problem hiding this comment.
Bug: NPM Workflow Triggers Unintended Releases
The NPM release workflow triggers on both release: published events and push to the develop branch, leading to unintended behavior:
- Unintended GitHub Releases: Pushes to
developwill attempt to create a GitHub release if one doesn't exist for the current package version, potentially creating releases from development commits. - Unintended NPM Publishing: The
build-and-publishandpublish-npmjobs run unconditionally, even if thecreate-releasejob skipped creating a release. This results in the package being published to NPM on everydeveloppush, and causes unnecessary rebuilds and re-publishing when triggered by an already published release.
.github/workflows/npm-release.yml#L2-L11
libCacheSim/.github/workflows/npm-release.yml
Lines 2 to 11 in a196791
.github/workflows/npm-release.yml#L71-L74
libCacheSim/.github/workflows/npm-release.yml
Lines 71 to 74 in a196791
BugBot free trial expires on June 25, 2025
You have used $0.00 of your $20.00 spend limit so far. Manage your spend limit in the Cursor dashboard.
Was this report helpful? Give feedback by reacting with 👍 or 👎



npm install libcachesimfrom the pre-build binaries in different platforms