ci: restore semantic-release commit-analyzer in release config#84
Closed
onesignal-deploy wants to merge 1 commit into
Closed
ci: restore semantic-release commit-analyzer in release config#84onesignal-deploy wants to merge 1 commit into
onesignal-deploy wants to merge 1 commit into
Conversation
sherwinski
changed the title
sherwinski
force-pushed
the
user-api-updates
branch
from
282faac to
9a507b4
Compare
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
2 participants
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
Adds
@semantic-release/commit-analyzer(conventionalcommits preset) to.releaserc.json. This is the only file changed in this PR.Why
A prior upstream change added
@semantic-release/exec(configured withsuccessCmdonly) to the release config. Because@semantic-release/execimplements theanalyzeCommitslifecycle step, semantic-release stopped auto-injecting its default@semantic-release/commit-analyzer— so the release step had no plugin to determine the version bump and every run reported "no relevant changes, so no new version is released." Listing@semantic-release/commit-analyzerexplicitly restores commit analysis.No package/code/docs changes are included here.