release-please-action
release-please-action copied to clipboard
automated releases based on conventional commits
### TL;DR Setting the option `include-component-in-tag: true` has no effect, no matter whether you set it in the workflow file or the manifest file. ### Expected behavior When setting the...
### TL;DR Per [the docs](https://github.com/googleapis/release-please?tab=readme-ov-file#how-do-i-change-the-version-number), previously I could force a version by adding `Release-As: 0.2.0` somewhere in the body of the commit message used in the squash-merge to main regardless...
### TL;DR I clicked [the link for ruby config in the README](https://github.com/google-github-actions/release-please-action/blob/cc61a07e2da466bebbc19b3a7dd01d6aecb20d1e/README.md?plain=1#L148) and it took me to an archived repository, from which I had to follow additional links, and which...
### TL;DR Is there plans to add as a GH app? https://github.com/organizations/MyOrg/settings/apps We use PATs but they are tied to a user/org. ### Detailed design _No response_ ### Additional information...
### TL;DR Getting `Error: release-please failed: Cannot read properties of undefined (reading 'replace')` ### Expected behavior Release-please completes successfully. This is the end of the log for a working run......
### TL;DR When you add a `path` parameter to the action, it doesn't use it to configure the strategy. We have a Helm chart with a `Chart.yaml` in `/chart/Chart.yaml`, but...
### TL;DR Trying to re-release old versions even with manifest config ### Expected behavior The correct versions to be released ### Observed behavior Please see: https://github.com/cha0s/flecks/pull/26/files You can see right...
### TL;DR We [migrated to v4](https://github.com/mdn/yari/pull/10122), but our [configured `changelog-sections`](https://github.com/mdn/yari/blob/c9f15220c62aee979a39e446890f8426263b5198/.release-please-manifest.json#L2-L7) are no longer taken into account, so the [v4 release PR](https://github.com/mdn/yari/pull/10407) is missing the "Miscellaneous" section (whereas the [v3 release...
### TL;DR When using `google-github-actions/release-please-action@v4`, specifying custom prefixes in `release-please-config.json` is not working, and instead the action ends in a "No user facing commits found since ... - skipping" message....
### TL;DR When using `release-please-action` with `skip-github-pull-request: true` on a `main` branch after a squash merge, no release is created despite the action completing successfully. ### Expected behavior I expected...