Skip to content

Conversation

@eKoopmans
Copy link
Owner

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:

  1. commit-analyzer > analyzeCommits determines what kind of release to make
  2. semantic-release internally determines the new package version based on that release info
  3. ... other steps happen, e.g. generateNotes
  4. npm > prepare updates the package.json version
  5. semantic-release.plugin.build.js (my new plugin) runs npm run build, generating a new dist folder
  6. git > prepare creates the release commit with changes from dist and package*.json
  7. ... other steps happen, e.g. npm publishing

In the future I'll be removing dist from 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:

@eKoopmans eKoopmans merged commit af78233 into main Jul 1, 2024
@eKoopmans eKoopmans deleted the chore/semantic-release-with-build branch July 1, 2024 04:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants