conventional-changelog
changelog
Our great sponsors
| conventional-changelog | changelog | |
|---|---|---|
| 11 | 3 | |
| 7,563 | 281 | |
| 1.2% | 1.1% | |
| 9.0 | 7.4 | |
| 3 days ago | 12 days ago | |
| TypeScript | JavaScript | |
| 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.
changelog
-
Semantic release to npm and/or ghcr without any tooling
@semantic-release/changelog - generates a fancy changelog using the repository name the workflow was run for as a title and cool emojis [example]
-
Automatically update git major tags on GitHub marketplace release
@semantic-release/changelog
-
How do you automate the release notes of your apps for release?
I started using this though it takes some getting used too https://github.com/semantic-release/changelog
What are some alternatives?
keep-a-changelog - If you build software, keep a changelog.
semantic-release-gitmoji - ✨🐛💥 A semantic-release plugin for gitmojis. Different from conventional changelog, Gitmoji commits are used to determine a release type and generate release notes.
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
Release It! 🚀 - 🚀 Automate versioning and package publishing
git-cliff - A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️
semantic-release-codeartifact - A semantic-release plugin for publishing packages to AWS CodeArtifact
semantic-release - :package::rocket: Fully automated version management and package publishing
release-please - generate release PRs based on the conventionalcommits.org spec
commit-analyzer - :bulb: semantic-release plugin to analyze commits with conventional-changelog
rn-boilerplate - React native boilerplate with formik, ui kittens, eslint setup, and expo
npm - :ship: semantic-release plugin to publish a npm package