auto
Generate releases based on semantic version labels on pull requests. (by intuit)
semantic-release
:package::rocket: Fully automated version management and package publishing (by semantic-release)
SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
| auto | semantic-release | |
|---|---|---|
| 2 | 76 | |
| 2,191 | 19,802 | |
| 0.8% | 0.8% | |
| 8.7 | 9.4 | |
| 20 days ago | 5 days ago | |
| TypeScript | JavaScript | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
auto
Posts with mentions or reviews of auto.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-17.
-
Package Publishing Reading & Resources
Auto - Intuit - Automates releases based on pull request labels. I used this at a previous job and appreciated that it didn't require linting commit messages or any extra effort from contributors. The downside, Lerna is a must for use with monorepos.
-
Minimal viable continuous delivery example repo
Automatically generates releases based on semantic version for every merge into the main branch (using intuit/auto)
semantic-release
Posts with mentions or reviews of semantic-release.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-30.
-
💡Automatic Deployment of your project dependencies updates on GCP : Efficiency vs. Cost?
Auto-tagging a project, Renovate or Dependabot can do this. With a Git Workflow and another tool like semantic-release you can do this. This behavior is a “gymnastic” to do on the CI/CD of your project but it’s not complicated. For example with GitLab CI, you can verify the pipeline run on the default branch of your project :
- 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 alternatives?
When comparing auto and semantic-release you can also consider the following projects:
Release It! 🚀 - 🚀 Automate versioning and package publishing
GitVersion - From git log to SemVer in no time
Doctrine Migrations - Doctrine Database Migrations Library
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
watermelon-vscode - 🍉 VS Code Extension to enrich files of code with code context
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
release-drafter - Drafts your next release notes as pull requests are merged into master.
minimalcd - Minimal viable Continuous delivery (CD) setup
commitlint - 📓 Lint commit messages
gradle-git-versioner - A Gradle plugin to automatically version a project based on commit messages and semantic versioning principles
semver - Semantic Versioning Specification
auto vs Release It! 🚀
semantic-release vs GitVersion
auto vs Doctrine Migrations
semantic-release vs standard-version
auto vs watermelon-vscode
semantic-release vs Release It! 🚀
auto vs Dokku
semantic-release vs release-drafter
auto vs minimalcd
semantic-release vs commitlint
semantic-release vs gradle-git-versioner
semantic-release vs semver