dhoulb / multi-semantic-release

Proof of concept that wraps semantic-release to work with monorepos.

dhoulb/multi-semantic-release Issues

pnpm version fails
Updated 13 days ago6
support esm
Updated 13 days ago8
Releasing from GitHub Actions npm ERR!! code ENEEDAUTH
Closed 3 years ago17
Coordination
Closed 6 months ago2
Strange behaviour when using this package: npm install is invoked on prepare step
Closed 8 months ago5
Publish after changes on the project root
Closed a year ago3
Omit workspace packages from the Dependencies section of release notes
Updated a year ago2
How to create a main release on the root of the monorepo
Updated a year ago
Leftover git tags after deployment failure
Updated a year ago3
@semantic-release/npm does not publish the content of the dist directory
Updated a year ago1
Newly added packages update all issues and prs in the history
Updated a year ago11
Unreleased packages should still trigger dependent releases
Updated a year ago1
npm publishing with wrong version tag
Updated a year ago4
Unable to run all tests locally
Updated a year ago2
GitHub Rate Limiting
Closed a year ago3
Error: git fetch --tags --update-head-ok
Closed a year ago5
Incorrect replacement of `workspace:^` drops caret in resolved dependency version
Closed 2 years ago1
[question] there is a way to retrieve depsUpdate on another plugin ?
Updated 2 years ago2
npm ERR! code EUNSUPPORTEDPROTOCOL when using yarn's "workspace:"
Updated 2 years ago7
Failed step "prepare" of plugin "Inline plugin"
Updated 2 years ago1
bug: replace pnpm `workspace:^` correctly
Closed 2 years ago4
Run script after successful release
Closed 2 years ago4
Encounter error when run multi-semantic-release
Closed 2 years ago2
question: plan or thought on upgrading to latest semantic-release version
Closed 2 years ago7
support for workspace protocol
Closed 3 years ago7
update-deps not working correctly
Closed 2 years ago1
there's a way to create only tags and avoid releases?
Updated 2 years ago2
ERELEASEBRANCHES The release branches are invalid in the `branches` configuration.
Updated 2 years ago1
Rate Limit
Closed 2 years ago3
not production recommended - always obsolate
Updated 2 years ago3
MSR fails on npm version step in workspaces
Closed 2 years ago4
How to release a beta version from a specific version?
Closed 2 years ago3
question: can MSR define plugin's default options ?
Updated 2 years ago
feature request: also bump deps in package distribution folder
Closed 2 years ago1
Skip/Customize publish step
Updated 2 years ago
doc: error when using * as recommended
Updated 2 years ago3
question: how to actually publish multiple packages to npm ?
Closed 2 years ago1
How to initially realease?
Closed 2 years ago20
SyntaxError: Package name must be non-empty string: "path/to/package.json"
Closed 2 years ago2
Is dependent versioning available?
Closed 2 years ago2
Bug or Feature Request: Publish GitHub tags with own files (dist) instead of whole project
Updated 3 years ago2
Multi-semantic-release changes the "workspace:^" while versioning
Closed 3 years ago3
package-lock.json is not updated
Closed 3 years ago3
[BUG] can't resolve workspace packages on windows
Closed 3 years ago4
new fix ignore private packages :(
Closed 3 years ago8
BUGS: Invalid local dependency version
Closed 3 years ago12
Release note generation disagreeing with package.json
Closed 3 years ago6
generateNotes error after merging pull request
Closed 3 years ago3
combined release commit
Updated 3 years ago4
use compatible version `^` when update local deps
Closed 4 years ago2