Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 2 commits
- 9 files changed
- 4 contributors
Commits on Nov 12, 2024
-
* feat: add "always-update" config option Fixes #1459 This patch adds a new option "always-update" that forces existing pull requests to be updated even when there are no changes to the release notes. This is useful, for example, when the repository enforces pull requests to be up-to-date with the main branch before they can be merged. Without this option set to `true`, that is, with the default behavior of release-please, if the last commit made to the main branch does not appear in the release notes, the existing pull request branch would not be rebased. * feat: apply suggested changes --------- Co-authored-by: Fabian Meyer <3982806+meyfa@users.noreply.github.com> Co-authored-by: Jeff Ching <chingor@google.com>
3 people authoredNov 12, 2024
Commits on Nov 13, 2024
-
chore(main): release 16.15.0 (#2429)
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v16.14.4...v16.15.0