monodeploy
monodeploy copied to clipboard
tophat
:monorail: Like semantic-release and Lerna, but for Yarn modern workspaces
**Is your feature request related to a problem? Please describe.** Useful if a changelog entry was skipped/not pushed due to a bug or issue at the end of the pipeline.
**Is your feature request related to a problem? Please describe.** Better to fail early if missing auth in non-dry run mode. **Describe the solution you'd like** Some sort of config...
**Is your feature request related to a problem? Please describe.** This functionality is currently supported by semantic release via the semantic release bot. Should be fairly simple to add as...
You may see a warning if you are using `yarn from sources` with monodeploy. In most cases this is fine. Some plugins will just be disabled.
**Describe the bug** When running `yarn monodeploy --dry-run` in the root of the repository where `packages/*` are set as workspaces, `monodeploy` seems to try to publish the root "package" as...
**Describe the bug** The error: ``` ➤ YN0001: │ Error: Executing 'git pull --rebase --no-verify origin' failed with code: 128 error: cannot pull with rebase: You have unstaged changes. error:...
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more. > [!WARNING] These dependencies are deprecated: | Datasource | Name | Replacement PR? |...
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "renovate[bot] avatar"){kind=avatar}
**Describe the bug** If your CI is building and autocommiting Commit 1, and Commit 2 is introduced between the initial merge and the autocommit, then monodeploy will fail to pull...
[](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [node](https://togithub.com/nodejs/node) | final | major | `20-slim` -> `21-slim` | ---...
## Description Updates to Yarn 4.1.1. Some checksum changes in Yarn 4.1.0 are possibly causing the yarn.lock to regress back to the 4.0.1 version when monodeploy commits changelog and package.json...
