release-please-action icon indicating copy to clipboard operation
release-please-action copied to clipboard

automated releases based on conventional commits

Results 138 release-please-action issues
Sort by recently updated
recently updated
newest added

### TL;DR I'd like to see a way to trigger "release-please" release manually via GitHub actions (given the `workflow_dispatch` field is enabled). ### Detailed design ```markdown I'm not sure that...

type: question

Is there better documentation somewhere which explains the setup and support for mono repos? Specifically I need the node release type to support `lerna publish` from `standard-version --lerna-package=*` where `*`...

type: docs
priority: p3

### TL;DR There are limitations to when other GitHub actions are triggered if you are using the default `GITHUB_TOKEN` https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#triggering-new-workflows-using-a-personal-access-token We should emphasize the fact that you probably want to...

type: docs
priority: p3

The README.md example release-please.yml sets `package-name: release-please-action`. This is good for unscoped packages but for `package-name: "@myorg/package"` it is mandatory to quote the scoped package name. This tripped me up...

type: docs
priority: p3

We should document the outputs set by manifest releases, e.g., `path--tag_name`, `releases_created`.

type: docs
priority: p3

I am attempting to test with a simple monorepo with two projects. A vue.js frontend and a golang backend. I've attempted to setup an action for each along with the...

type: docs
priority: p3

Is it possible to undo a release, and if so, can you please document how to do this? If for any reason there is an error in a release that...

type: docs
priority: p3

_Should document "releases_created" which manifest releaser sets rather than "release_created"_

type: docs
priority: p3

### TL;DR "‼ There are untagged, merged release PRs outstanding - aborting" is the last line of release-please output in GitHub Actions log. Happens in RPA v3 but not in...

type: bug
priority: p2

### TL;DR The custom value for the `pull-request-title-pattern` option in the workflow has no effect: the default pull request title is being used instead. ### Expected behavior The action uses...

type: bug
priority: p3