semantic-release
gradle-git-versioner
Our great sponsors
semantic-release | gradle-git-versioner | |
---|---|---|
75 | 1 | |
19,738 | 21 | |
1.4% | - | |
9.4 | 6.9 | |
5 days ago | 4 months ago | |
JavaScript | Kotlin | |
MIT 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.
semantic-release
- alacritty-themes not working any more!!!
- Announcing @ngneat/avvvatars
- Auto versioning?
-
Is it possible to bypass merge queue requirement for a GitHub app without needing admin permissions?
I'm trying to improve the security behind our release process, which uses semantic-release. During this process, it creates a change log which is committed to the repo, publishes a package and a few other things.
-
How to set up Commitzen with Husky
Conventional commits specification contains a set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of, for example, semantic release. You can manually follow this convention in your project or use a tool to assist you, such as Commitizen.
-
Automated release with Semantic Release and commitizen
When working with JavaScript projects, managing version numbers and commit messages is important for the maintainability of the project. Since 2020 I have been the main developer of Atomic Calendar Revive a highly customisable Home Assistant calendar card, I found maintaining versions and releases to be cumbersome until recently. In this article, I will introduce the commitizen and semantic-release packages for creation or appropriate commit messages and semantic versioning. I will also provide examples of how I am currently using these packages to streamline my release workflow and project maintenance.
- π¦ Effortless Data Quality w/duckdb on GitHub βΎοΈ
-
How I Sliced Deployment Times to a Fraction and Achieved Lightning-Fast Deployments with GitHub Actions
To further streamline deployments, I introduced semantic-release. This tool automates commit tagging and tracks changes since the previous version. As a result, deployments now occur only when new tags are present, saving us valuable minutes.
- Automated Release Notes in Azure Devops
-
What are some examples of good release notes from open source projects that you have come across?
If your projects ar made in javascript and related tools, I'd suggest you to check: semantic-release
gradle-git-versioner
-
Artifact/Package versioning
I use this https://github.com/toolebox-io/gradle-git-versioner It just automatically creates a version for you in every commit. You can configure it the way you want. You just need to add a tag to the last commit of the development, or if you want, in the PR Merge with [major | minor | patch] and the plugin does everything for you without any hassle.
What are some alternatives?
GitVersion - From git log to SemVer in no time
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
gradle-jgitver-plugin - gradle plugin that defines automatically project version using jgitver
Release It! π - π Automate versioning and package publishing
gotagger - A CLI and library for managing versions and git tags based on conventional commit messages.
release-drafter - Drafts your next release notes as pull requests are merged into master.
maven-git-versioning-extension - This extension will set project version, based on current Git branch or tag.
commitlint - π Lint commit messages
Gradle buildSrcVersions - Life is too short to google for dependencies and versions
semver - Semantic Versioning Specification
cz-cli - The commitizen command line utility. #BlackLivesMatter