fix: Update release process and version handling in pipeline#71
Merged
jamesvillarrubia merged 4 commits intomainfrom Oct 7, 2025
Merged
fix: Update release process and version handling in pipeline#71jamesvillarrubia merged 4 commits intomainfrom
jamesvillarrubia merged 4 commits intomainfrom
Conversation
…lish steps - Updated CLI to read version from package.json dynamically instead of using placeholder - Excluded bin directory from CJS build (only ESM bin is used) - Removed redundant chmod from CJS build script - Configured release-it to skip npm publish (handled separately in workflow) - Updated GitHub Actions workflow to explicitly run build after version bump - This ensures published npm package has correct version in --version output
…kflow - Updated npm.publish to false in .release-it.js example - Added explicit build step after version bump in workflow examples - Added separate npm publish step with NODE_AUTH_TOKEN - Applied changes to both release and prerelease job examples
jamesvillarrubia
changed the title
jamesvillarrubia
changed the title
The bin directory is excluded from CJS builds because it uses import.meta.url which is only available in ESM. Only the ESM bin is used as the executable.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #71 +/- ##
=======================================
Coverage 98.91% 98.91%
=======================================
Files 3 3
Lines 736 736
Branches 75 75
=======================================
Hits 728 728
Misses 7 7
Partials 1 1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…flag - Modified pullcraft.ts to use VERSION_PLACEHOLDER that gets replaced at bundle time - Updated build.bundle.js to read version from package.json and inject via esbuild define - Removed --experimental-default-type=module flag from build.sea.js (incompatible with Node v23) - Version now works correctly for both npm installs and SEA bundles
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.
Summary
Type: fix
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
Does this PR introduce a breaking change?
**Has Testing been included for this PR?
Other Information
The changes ensure that the build uses the most recent version number, which is crucial for accurate releases. The modification in `.release-it.cjs` to disable automatic npm publishing aligns with the new manual publish steps added in the GitHub Actions workflow.
This update is crucial for maintaining accurate versioning and improving the reliability of the release process in automated environments.