release-please-action
release-please-action copied to clipboard
google-github-actions
automated releases based on conventional commits
### TL;DR I have a project with four crates, two of which are handled by release-please-action. The second crate depends on the first, but its `Cargo.toml` does not get updated...
### TL;DR Existing projects are having their versions reset to 1.0.0 because the `package-name` is being included as a prefix when searching for the latest released version. I've left [a...
### TL;DR I'll try to be as helpful as I can, but the `release-please` output cuts some of it and I'm not familiar with it's internal logic. We've been successfully...
### TL;DR Release-please was working fine. After moving the repo to a new organization, it fails suddenly. ### Expected behavior working without error as nothing has been changed ### Observed...
### TL;DR Two releases, one Elixir release from the root path (`.`) and another Node release from the `assets/` path fails with a not found error on the assets path....
### TL;DR After adding an iconography package, release actions take a long time to make a decision and thus complete the action task. Previously the task would complete in less...
### TL;DR I would like for the generated `CONTRIBUTING.md` and `.release-please-manifest.json` formatting to be `prettier`-compliant. ### Detailed design ```markdown Could be a wrapper around the core logic that's already in...
### TL;DR When using `"separate-pull-requests": true` with multi-package release-please config you can have 2 chore PRs opened at the same time as a result of 2 different changes in different...
I was testing out a release config today and possibly due to some misconfig on my part I ended up with https://github.com/bharathkkb/mono-bp-test/runs/2661822325?check_suite_focus=true Then subsequent runs showed as passed but actually...
https://github.com/gengjiawen/monkey-rust/pull/28 @bcoe @fasterthanlime
Metadata
Owner
Metadata
automated releases based on conventional commits