build(deps): bump google-github-actions/release-please-action from 2 to 4 #2961
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [google-github-actions/release-please-action](https://github.com/google-github-actions/release-please-action) from 2 to 4. - [Release notes](https://github.com/google-github-actions/release-please-action/releases) - [Changelog](https://github.com/google-github-actions/release-please-action/blob/main/CHANGELOG.md) - [Commits](google-github-actions/release-please-action@v2...v4) --- updated-dependencies: - dependency-name: google-github-actions/release-please-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
cclauss
deleted the
dependabot/github_actions/google-github-actions/release-please-action-4
branch
|
Sorry I didn't reply even though the bot tagged me in this PR... This bump had breaking changes that would require a total re-write of the configuration files. See "BREAKING CHANGES" here: https://github.com/google-github-actions/release-please-action/releases/tag/v4.0.0 I don't think release-please-action is working in this repo anymore after the bump, see CI warnings here: https://github.com/nodejs/node-gyp/actions/runs/7596312708/job/20689880404#step:2:1
I would suggest a revert until/unless anyone is willing to read up on the new "manifest-based configuration" approach, which is what newer release-please versions mandate for any sort of serious customization. I tried to look into it and it was a bit much for me to understand. We'd need to re-write our whole congifuration for release-please to keep using the custom commit prefixes such as Anyway, I don't have time to look into it personally. Sorry. Please consider reverting release-please-action back to 2.x, or seeing if de-bumping to 3.x will work without config file changes. Best Regards, |
Bumps [google-github-actions/release-please-action](https://github.com/google-github-actions/release-please-action) from 2 to 4. - [Release notes](https://github.com/google-github-actions/release-please-action/releases) - [Changelog](https://github.com/google-github-actions/release-please-action/blob/main/CHANGELOG.md) - [Commits](google-github-actions/release-please-action@v2...v4) --- updated-dependencies: - dependency-name: google-github-actions/release-please-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps google-github-actions/release-please-action from 2 to 4.
See:
release-please-actionfor automated releases #2395Release notes
Sourced from google-github-actions/release-please-action's releases.
... (truncated)
Changelog
Sourced from google-github-actions/release-please-action's changelog.
... (truncated)
Commits
cc61a07chore(main): release 4.0.2 (#909)8bf1247chore: build dist (#908)2a496d1fix: log release-please version (#910)ba1c241docs: fix small typo in README.md (#907)df71963fix: bump release-please from 16.4.0 to 16.5.0 (#905)a2d8d68chore(main): release 4.0.1 (#899)650da25cleanup: use built-in release-please types (#900)6908db2chore: build dist (#898)2463dadfix: bump release-please from 16.3.1 to 16.4.0 (#897)18e07ccdocs: update versions in readme.md (#893)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)