exec
semantic-release
Our great sponsors
exec | semantic-release | |
---|---|---|
4 | 75 | |
123 | 19,802 | |
2.4% | 1.7% | |
7.0 | 9.4 | |
5 days ago | 4 days ago | |
JavaScript | 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.
exec
-
Semantic release to npm and/or ghcr without any tooling
@semantic-release/exec - used to set GitHub action environment variables when run as from docker container and GitHub action outputs when run as a marketplace action
-
Automatically update git major tags on GitHub marketplace release
This meant that forcing a major tag update with @semantic-release/exec as part of the release process was possible, but would result in the major tag (for example v3) linking to a valid repository commit SHA that is not actually released in the marketplace.
-
A complete guide to use dependabot with semantic-release and @vercel/ncc for GitHub Actions
This article introduces semantic-release as a solution. It automates the release process, and its exec plugin helps us to run @vercel/ncc before the release automatically.
-
You donβt need semantic-release (sometimes)
You may need a minor tweak up. For example, push some pkg to both public and internal registries. Ooops. "...publishing to two different registry is not a good idea". In this case you can not rely on stable, convenient and tested in millions runs semrel/npm plugin, and you have to just write a pair of commands by hand with semantic-release/exec instead:
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
What are some alternatives?
Discord-Hide-Blocked-Messages - Ways to hide discords "1 blocked message - show message" buttons
GitVersion - From git log to SemVer in no time
setup-buildx-action - GitHub Action to set up Docker Buildx
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
zx - A tool for writing better scripts
Release It! π - π Automate versioning and package publishing
semantic-release-docker - semantic-release plugin to build and push docker images
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
npm - :ship: semantic-release plugin to publish a npm package
gradle-git-versioner - A Gradle plugin to automatically version a project based on commit messages and semantic versioning principles