exec
semantic-release-gh-pages-plugin
Our great sponsors
| exec | semantic-release-gh-pages-plugin | |
|---|---|---|
| 4 | 2 | |
| 123 | 23 | |
| 2.4% | - | |
| 7.0 | 7.0 | |
| 5 days ago | 5 days ago | |
| JavaScript | TypeScript | |
| 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-gh-pages-plugin
-
📜 Better collab flows w. (git) Conventional Commits
semantic-release-gh-pages-plugin
-
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:
What are some alternatives?
Discord-Hide-Blocked-Messages - Ways to hide discords "1 blocked message - show message" buttons
zx-semrel - `zx`-based release script as `semantic-release` alternative (PoC)
setup-buildx-action - GitHub Action to set up Docker Buildx
npm - :ship: semantic-release plugin to publish a npm package
semantic-release - :package::rocket: Fully automated version management and package publishing
semantic-release-helm - semantic-release plugin to update appVersion in a Helm chart
zx - A tool for writing better scripts
release-please - generate release PRs based on the conventionalcommits.org spec
semantic-release-docker - semantic-release plugin to build and push docker images
semantic-release-monorepo-hooks - Workarounds to handle `semantic-release-monorepo` multipublishing
multi-semantic-release - Proof of concept that wraps semantic-release to work with monorepos.