conventional-changelog
actions-tagger
Our great sponsors
| conventional-changelog | actions-tagger | |
|---|---|---|
| 11 | 1 | |
| 7,563 | 128 | |
| 1.2% | 3.9% | |
| 9.0 | 8.0 | |
| 1 day ago | 2 months ago | |
| TypeScript | TypeScript | |
| ISC License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
conventional-changelog
-
Using semantic-release to automate releases and changelogs
conventional-changelog-conventionalcommits is a package used for creating conventional commits and has a bit more configuration possibilities with changelogs in contrast to the default Angular commit scheme.
-
Conventional Commits - Specification for Your Commit Messages
Finally, it is also interesting to be able to automatically generate the CHANGELOG file from the commit messages. There are various tools for this, one of them is Conventional Changelog
-
Minor imperfections that shout ‘beginner code’
Some projects generate change logs automatically from commits. For example, angular uses conventional-changelog.
- GitHub Actions can't find built binaries to put them to a release
- FRONT END - LINKS CRIATIVOS E TÉCNICOS
-
Confused about how to get my packages up to `1.0.0` using Lerna / Conventional commits...
I'm under the understanding from this issue that in semver, a package that is <1.0.0 is considered unstable. This means that a breaking change can occur at any version, usually between minors.
-
Automatically update git major tags on GitHub marketplace release
conventional-changelog-conventionalcommits
-
Keep a Changelog
[1] - https://github.com/conventional-changelog/conventional-chang...
-
What are some good practices for writing changelogs/update notes?
I dont use myself, but some people follows something like the conventional commit spec, and then uses a generator.
-
Automated versioning and package publishing using GitHub Actions and semantic-release
@semantic-release/commit-analyzer It determines the type of our release (e.g. major, minor, patch) by analyzing commits with conventional-changelog. semantic-release uses Angular Commit Message Conventions by default.
actions-tagger
-
Automatically update git major tags on GitHub marketplace release
Actions-R-Us/actions-tagger@v2 - updates major tag on release
What are some alternatives?
keep-a-changelog - If you build software, keep a changelog.
git - :twisted_rightwards_arrows: semantic-release plugin to commit release assets to the project's git repository
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
npm - :ship: semantic-release plugin to publish a npm package
git-cliff - A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️
commit-analyzer - :bulb: semantic-release plugin to analyze commits with conventional-changelog
Release It! 🚀 - 🚀 Automate versioning and package publishing
semantic-release-docker - semantic-release plugin to build and push docker images
release-please - generate release PRs based on the conventionalcommits.org spec
changelog - :blue_book: semantic-release plugin to create or update a changelog file
rn-boilerplate - React native boilerplate with formik, ui kittens, eslint setup, and expo
setup-cpp - Install all the tools required for building and testing C++/C projects.