This repository has been archived by the owner on Aug 29, 2023. It is now read-only.
chore: Semantic release #27
Merged
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
Closed
anthonypecchillo
added a commit
that referenced
this pull request
Jun 23, 2023
* chore: add semantic-release dependency * chore: init semantic release GitHub workflow * fix: bump node version in CI to LTS * chore: add "semantic-release" script to package.json
anthonypecchillo
added a commit
that referenced
this pull request
Jun 24, 2023
* chore: transpile modern JS features for older browsers * chore: Semantic release (#27) * chore: add semantic-release dependency * chore: init semantic release GitHub workflow * fix: bump node version in CI to LTS * chore: add "semantic-release" script to package.json * chore: transpile modern JS features for older browsers * fix: update package-lock after rebase * fix: resolve post-rebase issues (part 1) * fix: resolve post-rebase issues (part 2)
|
🎉 This PR is included in version 0.1.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Semantic Release
Resolves #26.
Summary
Automates the publishing of updates for @sort/react-components to NPM.
Changes
release.yml. Relies on semantic-release.test.ymlto LTS.How It Works
Using
fix:,feat:, etc. in Commit Messages:Conventional commits prefix commit messages with a type, which communicates the kind of changes that have been made in the commit. The most common types include:
fix:This indicates a bug fix, and correlates with PATCH in semantic versioning. Patch release (increments the last number). E.g., 1.0.1 -> 1.0.2Example commit message:
fix: correct minor typos in codefeat:This indicates a new feature, and correlates with MINOR in semantic versioning. Minor release (increments the middle number). E.g., 1.0.1 -> 1.1.0Example commit message:
Breaking Changes
For both
fix:andfeat:, if you append a!after the type/scope, it is interpreted as a BREAKING CHANGE, which correlates with MAJOR in semantic versioning. Major release (increments the first number). E.g., 1.0.1 -> 2.0.0Example commit message:
Other Commit Types
Other types include
chore:,docs:,style:,refactor:,perf:,test:, and others.These types don't correlate with semantic versioning and don't trigger a release when used alone. They can be used to provide a more granular view of what work was done in the commit.
Always follow the type with a colon and a space, then provide a short, descriptive message about the changes. For example:
Note: On Revert Commits
revert:, followed by the header of the reverted commit.