Gathering detailed insights and metrics for semantic-release-monorepo-hooks
Gathering detailed insights and metrics for semantic-release-monorepo-hooks
Gathering detailed insights and metrics for semantic-release-monorepo-hooks
Gathering detailed insights and metrics for semantic-release-monorepo-hooks
Workarounds to handle `semantic-release-monorepo` multipublishing
npm install semantic-release-monorepo-hooks
Typescript
Module System
Node Version
NPM Version
JavaScript (92.62%)
Shell (7.38%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
33 Stars
137 Commits
4 Forks
8 Watchers
9 Branches
5 Contributors
Updated on Apr 15, 2023
Latest Version
2.10.0
Package Id
semantic-release-monorepo-hooks@2.10.0
Unpacked Size
26.31 kB
Size
8.67 kB
File Count
24
NPM Version
8.9.0
Node Version
18.2.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
5
Workaround to handle semantic-release-monorepo
multipublishing
This project provided invaluable experience in understanding how lerna and semantic-release work. Along with this came the realization that the approach needed to be changed. Here's the short note on the evolution of these ideas. Thus, today we suggest using multi-semantic-release as the best alternative:
Further development of this project seems futile. Anyway, we will regularly apply vulnerability patches for as long as possible. Thank you all for your feedback, PRs, downloads and stars.
lerna
-based repos aka monorepos
out of box.1[Semantic release]: Found 0 commits for package *** since last release
1 npm i -D semantic-release 2 npm i -D semantic-release-monorepo 3 npm i -D semantic-release-monorepo-hooks
and plugins:
1{ 2 "devDependencies": { 3 "@semantic-release/changelog": "^3.0.1", 4 "@semantic-release/commit-analyzer": "^6.1.0", 5 "@semantic-release/git": "7.0.5", 6 "@semantic-release/github": "5.2.1", 7 "@semantic-release/npm": "5.0.5", 8 "@semantic-release/release-notes-generator": "7.1.2", 9 "lerna": "^3.4.3", 10 "semantic-release": "15.10.6", 11 "semantic-release-monorepo": "6.1.1", 12 "semantic-release-monorepo-hooks": "2.6.2", 13 "semantic-release-plugin-decorators": "^2.0.0" 14 } 15}
.releaserc.js
1 const hooks = require('semantic-release-monorepo-hooks') 2 const output = hooks() 3 4 module.exports = { 5 branch: 'master', 6 tagFormat: 'v${version}', 7 prepare: [ 8 '@semantic-release/changelog', 9 '@semantic-release/npm', 10 { 11 'path': '@semantic-release/git', 12 'message': 'chore(' + output.package + '): release ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}' 13 } 14 ], 15 publish: [ 16 '@semantic-release/npm' 17 ], 18 verifyConditions: [ 19 '@semantic-release/npm', 20 '@semantic-release/git' 21 ], 22 monorepo: { 23 analyzeCommits: [ 24 '@semantic-release/commit-analyzer' 25 ], 26 generateNotes: [ 27 '@semantic-release/release-notes-generator' 28 ] 29 } 30 };
.travis.yml
1deploy: 2 provider: script 3 skip_cleanup: true 4 script: 5 - yarn lerna exec --concurrency 1 "npx --no-install semantic-release -e semantic-release-monorepo" && node -e "require('semantic-release-monorepo-hooks').hookAfterAll()"
env
varsGH_TOKEN
and GH_USER
must be declared for git push
. See drop_last_tag.sh for details.
Hooks reverts some effects of previous semantic-release
run and returns info map as a result:
1 { 2 isModified: true, 3 isLastModified: false, 4 isLastRun: false, 5 total: 5, 6 processed: 1, 7 modified: 2, 8 modifiedPacks: [ '@qiwi/pijma-core', '@qiwi/pijma-desktop' ], 9 package: '@qiwi/pijma-core', 10 tag: 'v1.5.0\n', 11 run: 1 12 }
Take a look at multi-semantic-release. With --execasync
flag it produces the same effect but in a different way.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
packaging workflow detected
Details
Reason
security policy file detected
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 1/14 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
11 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More