chore: Make a custom semantic-release action with build step #702
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.
This PR should fix the semantic-release process to squeeze the build step in between when the NPM version is bumped and when the changes are committed and pushed.
The goal, in semantic-release:
commit-analyzer > analyzeCommitsdetermines what kind of release to makesemantic-releaseinternally determines the new package version based on that release infogenerateNotesnpm > prepareupdates the package.json versionsemantic-release.plugin.build.js(my new plugin) runsnpm run build, generating a newdistfoldergit > preparecreates the release commit with changes from dist and package*.jsonIn the future I'll be removing
distfrom git tracking, but regardless I want that build to happen in the middle so the bundle files can be generated with the right version and copyright etc.Resources: