shreemaan-abhishek opened a new pull request, #2131: URL: https://github.com/apache/apisix-website/pull/2131
## Summary - Bump APISIX version from 3.18.0 to 3.19.0 across website config files - Update release date to 2026-09-28 - Add version 3.19 to the versions list https://github.com/apache/apisix/blob/release/3.19/CHANGELOG.md#3190 The release date matches the publication time of the source artifacts on the ASF mirror (`https://downloads.apache.org/apisix/3.19.0/`, 2026-09-28), the same convention 3.17.0 and 3.18.0 followed, and `apache-apisix-3.19.0-src.tgz` is already published there so the download link resolves. ### Why this leaves `deploy.yml` alone The 3.18.0 release PR (#2106) had to update the "Assert canonical contract" fixture, because `mcp-bridge` shipped in 3.18 and the `next` page stopped being self-canonical. That fixture now pins the version-less canonical: ``` grep -q 'rel="canonical" href="https://apisix.apache.org/docs/apisix/plugins/mcp-bridge/";' "$f" ``` `docs/en/latest/plugins/mcp-bridge.md` is present in `release/3.19`, so the `next` page still resolves to a version-less page that exists and the assertion holds with 3.19 as the latest version. The comment left by #2106 asks for the self-canonical half to be fixtured again once a doc lands on `next` alone. That has not happened yet: `docs/en/latest` is identical between `master` and `release/3.19`, so every `next` doc also ships in the latest release. The comment stays accurate as written. -- 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]
