shreemaan-abhishek opened a new pull request, #14183:
URL: https://github.com/apache/apisix/pull/14183
### Description
Brings the 3.20.0 release back to `master`.
This branch is `release/3.20` (tip `9380e213`, from #14168) with `master`
merged in. `release/3.20` is PR-protected, and this repository merges PRs by
squash or rebase, so merging `master` into `release/3.20` itself would not give
the two branches a shared history. Merging on this branch instead puts the
merge base at the current `master` tip, so the diff shows only what the release
adds. `release/3.20` itself is unchanged.
The release changes, already reviewed in #14168:
- The `3.20.0` section in `CHANGELOG.md` and its Table of Contents entry.
- The version bump to `3.20.0` in `apisix/core/version.lua`,
`docs/{en,zh}/latest/config.json`, and the Admin API and Control API OpenAPI
documents (`docs/openapi/admin-api/openapi.yaml`, its bundle
`docs/en/latest/admin-api.json`, and `docs/en/latest/control-api.json`).
- `APISIX_DASHBOARD_COMMIT` in `.requirements` set to `e5e1457`.
The only code change on `release/3.20` after the cut is the backport of
#14167 (#14169), which `master` already has, so it does not show up in this
diff.
`check-changelog` passes once the `3.20.0` tag is pushed. Before that, the
script compares `3.19.0` against this PR's merge result, which also includes
the `master` commits made after `release/3.20` was cut. Those are not part of
3.20.0.
### Checklist
- [x] I have explained the need for this PR and the problem it solves
- [x] I have explained the changes or the new features added to this PR
- [ ] I have added tests corresponding to this change (N/A: release
bookkeeping only, no runtime code changes)
- [x] I have updated the documentation to reflect this change
- [x] I have verified that this change is backward compatible (this PR only
touches release metadata; the breaking changes it documents landed in their own
PRs and are listed in the `Change` section)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
