semantic-release-toolkit
semantic-release
semantic-release-toolkit | semantic-release | |
---|---|---|
1 | 77 | |
11 | 20,000 | |
- | 1.0% | |
2.4 | 9.4 | |
15 days ago | 9 days ago | |
TypeScript | JavaScript | |
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-toolkit
-
You donโt need semantic-release (sometimes)
Iโm a big fan of semantic-release since it appeared. I followed its development, studied its inners. I did in-house reports, held workshops and finally brought semrel to our build infrastructure. I wrote plugins, plugin-factories and testing-tools for it. For several years now, I've been trying to combine semantic releases and monorepositories in many OSS projects:
semantic-release
-
Git commit helper: add emojis to your commits
Using Conventional Commits โญ as a standard for your commit messages, makes Semantic Versioning ๐ as easy as can be, with tools like Conventional Changelog ๐ Standard Version ๐ and Semantic Release ๐ฆ๐
-
๐ก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.
What are some alternatives?
multi-semantic-release - Proof of concept that wraps semantic-release to work with monorepos.
GitVersion - From git log to SemVer in no time
npm - :ship: semantic-release plugin to publish a npm package
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
multi-semantic-release - Proof of concept that wraps semantic-release to work with monorepos.
Release It! ๐ - ๐ Automate versioning and package publishing
zx-semrel - `zx`-based release script as `semantic-release` alternative (PoC)
release-drafter - Drafts your next release notes as pull requests are merged into master.
semantic-release-monorepo-hooks - Workarounds to handle `semantic-release-monorepo` multipublishing
commitlint - ๐ Lint commit messages
exec - :shell: semantic-release plugin to execute custom shell commands
gradle-git-versioner - A Gradle plugin to automatically version a project based on commit messages and semantic versioning principles