
Security News
Deno 2.2 Improves Dependency Management and Expands Node.js Compatibility
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.
semantic-release-monorepo
Advanced tools
Plugins for `semantic-release` allowing it to be used with a monorepo.
Apply semantic-release
's automatic publishing to a monorepo.
The default configuration of semantic-release
assumes a one-to-one relationship between a Github repository and an npm
package.
This plugin allows using semantic-release
with a single Github repository containing many npm
packages.
Rather than attributing all commits to a single package, this plugin will automatically assign commits to packages based on the files that a commit touched.
If a commit touched a file within a package's root, it will be considered for that package's next release. Yes, this means a single commit could belong to multiple packages.
A push may release multiple package versions. In order to avoid version collisions, git tags are namespaced using the given package's name: <package-name>-<version>
.
This package is a complement to semantic-release
. It is assumed the user is already fully familiar with that package and its workflow.
npm install -D semantic-release-monorepo
In package.json
:
{
"release": {
"analyzeCommits": "semantic-release-monorepo",
"generateNotes": "semantic-release-monorepo",
"getLastRelease": "semantic-release-monorepo",
"publish": ["@semantic-release/npm", "semantic-release-monorepo/github"]
}
}
All semantic-release-monorepo
plugins wrap the default semantic-release
workflow, augmenting it to work with a monorepo.
Filters the repo commits to only include those that touched files in the given monorepo package.
Maps the gitTag
fields of lastRelease
and nextRelease
to use the monorepo git tag format.
Maps the version
field of nextRelease
to use the monorepo git tag format. The wrapped (default) generateNotes
implementation uses version
as the header for the release notes. Since all release notes end up in the same Github repository, using just the version as a header introduces ambiguity.
Addresses multiple problems identifying the last release for a monorepo package:
The wrapped (default) getLastRelease
plugin uses gitHead
from the npm
package metadata to identify the last release. However, npm
doesn't publish gitHead
as part of a package's metadata unless its package.json
and the repo's .git
are in the same folder (never true for a monorepo).
https://github.com/npm/read-package-json/issues/66#issuecomment-222036879
We can use semantic-release
's fallback strategy, searching for a git tag matching the latest npm
version, but we must map the git tag to the monorepo git tag format.
gitTag
field of nextRelease
to use the monorepo git tag format.FAQs
Plugins for `semantic-release` allowing it to be used with a monorepo.
The npm package semantic-release-monorepo receives a total of 25,668 weekly downloads. As such, semantic-release-monorepo popularity was classified as popular.
We found that semantic-release-monorepo demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.
Security News
React's CRA deprecation announcement sparked community criticism over framework recommendations, leading to quick updates acknowledging build tools like Vite as valid alternatives.
Security News
Ransomware payment rates hit an all-time low in 2024 as law enforcement crackdowns, stronger defenses, and shifting policies make attacks riskier and less profitable.