conventional-changelog
standard-version
Our great sponsors
conventional-changelog | standard-version | |
---|---|---|
11 | 13 | |
7,563 | 7,548 | |
1.2% | 0.7% | |
9.0 | 2.8 | |
1 day ago | 3 days ago | |
TypeScript | JavaScript | |
ISC License | ISC 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.
standard-version
-
Streamline Your Workflow: Setting Up Git Hooks with Husky to Simplify Version Updates
Dive deeper into the world of Husky with the official documentation. Explore the capabilities of Standard Version through its comprehensive documentation. Unravel the mysteries of semantic-release with its detailed documentation. Discover the versatility of bumpp with its comprehensive documentation.
-
Starting React Native Project in 2023
We can use standard-version tool to generate a changelog, bump the version of app and create a new tag automatically.
-
Microservices Shared Libraries — Design and Best Practices
There are many great tools to help with automation here, some of them are action-semantic-pull-request to enforce conventional commits and standard version to bump the version and create a changelog according to the conventional commits.
-
Add Commitint, Commitizen, Standard Version, and Husky to SvelteKit Project
I tried gitmoji and followed Make everyone in your project write beautiful commit messages using commitlint and commitizen by @sohandutta, but end up using the setting in this article because it's not compatible to changelog generation of standard-version (Ref: Issue #859)
-
Releasing a pomodoro app #1: programming bit by bit
As a bonus point, the issues you create in your repository can also serve as part of the documentation. You can outline new features there and you will even be able to generate changelogs from the merged pull requests (like I do using conventional-changelog/standard-version).
-
Taiga UI: A year in Open Source
There’s also a husky precommit hook with ESlint and Prettier fixing and formatting changed code on every commit with lint-staged which makes sure malformed code doesn't even make it to the Pull Request. Combined with standard-version and strict commit messages it makes releasing and changelog generation a breeze. For a contributor the workflow is as smooth as:
-
Autodeploy javascript library to npmjs via Github Actions
But you can also automate even more, if, for example, you write according to Conventional Commits, you can also automate the creation of tags using the standard-version library.
-
Automatically generate and release a changelog using Node.js
# Changelog All notable changes to this project will be documented in this file. See \[standard-version\](https://github.com/conventional-changelog/standard-version) for commit guidelines. ## 1.1.0 (2021-07-12) ### Features * **new-feature:** add a new-feature to our project 11c0322
-
Awesome Dev Tools To Automate Code Tasks 🔥
Standard Version
-
versionem - Simple and straightforward automated semantic versioning integrated to changelog generation
So this is like standard-version with less features?
What are some alternatives?
keep-a-changelog - If you build software, keep a changelog.
semantic-release - :package::rocket: Fully automated version management and package publishing
git-cliff - A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️
husky - Git hooks made easy 🐶 woof!
Release It! 🚀 - 🚀 Automate versioning and package publishing
semver - Semantic Versioning Specification
release-please - generate release PRs based on the conventionalcommits.org spec
towncrier - Manage the release notes for your project.
rn-boilerplate - React native boilerplate with formik, ui kittens, eslint setup, and expo
commitlint - 📓 Lint commit messages
react-hook-form - 📋 React Hooks for form state management and validation (Web + React Native)
changie - Automated changelog tool for preparing releases with lots of customization options