build(release): improve release logic #725
Closed
Conversation
This file contains 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
|
Oh, and by the way, I'm using most of these configs in the VSCode ShellCheck extension repository (along with the semantic-release-vsce plugin). So, feel free to browse the releases section of it to see some in action: https://github.com/vscode-shellcheck/vscode-shellcheck/releases |
|
Not applicable any longer since #791. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changing the preset to
conventionalcommitsensures that the commit message matches the current specification of Conventional Commits. Otherwise, the default isangularwhich is the AngularJS style. I always wanted that semantic-release shipped that by default, but unfortunately they don't have time to merge my PR.It also allows to use things like
fix!: drop support for somethingto indicate that the commit is a breaking change.I also configured semantic-release with some things that I judge to be more optimal, like triggering releases when a production dependency gets updated, or a refactoring or performance improvement gets merged. I found many versions released with non helpful changelogs because of this, like v2.7.0, and v2.6.4.
It also reduces the clutter from the changelog messages by skipping the update of development dependencies.
To finalize, the new configuration improves the GitHub Releases, since they now will get the npm
.tgzfiles as assets and there will be a link to the npmjs page of the release (like here).I hope you like it! :)