docs: Add F5 WAF for NGINX 5.14 release notes and OS support - #2150
Open
ohad-perets wants to merge 3 commits into
Open
docs: Add F5 WAF for NGINX 5.14 release notes and OS support#2150ohad-perets wants to merge 3 commits into
ohad-perets wants to merge 3 commits into
Conversation
github-actions
Bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
github-actions
Bot
added
the
tooling
mouraddmeiri
approved these changes
Jul 29, 2026
Add the 5.14 changelog entry and document support for the new operating systems, and unify the RHEL/Rocky Dockerfile partials. Changelog and specs: - Add "F5 WAF for NGINX 5.14" changelog section (NGINX OSS 1.31.3, NGINX Plus R37.0, Go 1.26.5; resolved issues 14828, 14924, 14990 and BD hardening); keep the existing 5.13.4 entry. - Update the supported OS matrix for Debian 13, Ubuntu 26.04, RHEL 10, and Rocky Linux 10. New OS support: - Add Rocky Linux 10 and Ubuntu 26.04 (Resolute Raccoon). - Add RHEL 10 and Rocky Linux 10 rows to IP intelligence packages. Dockerfile partial unification: - Replace per-version RHEL/Rocky partials with parameterized rhel-oss, rhel-plus, rocky-oss, rocky-plus partials (UBI_VERSION and ROCKY_VERSION, supporting 8, 9, and 10), in both the jwt-mount and nginx-plus-without-jwt-mount variants. - Collapse the RHEL and Rocky tabs in docker.md and kubernetes.md into single parameterized tabs. Fixes: - Correct the nginx package pin (1.25.5 -> 1.31.3) in the Debian and Ubuntu OSS partials. - Fix the single-container RHEL 9 and RHEL 10 Dockerfiles that incorrectly used Rocky Linux base images. - Fix the empty version variable in the Rocky OSS repo path. - Update Debian and Ubuntu codename comments. Note: the 5.14 build number and release date are placeholders (5.TBD.0 / TBD) pending the promoted build.
Replace hardcoded 5.2.0 image tags in the shared docker install include fragments with the version-waf-enforcer and version-waf-config-mgr shortcodes so they render the current release (5.14.0), matching the inline compose block on the same page.
ohad-perets
force-pushed
the
waf-release-5.14-docs
branch
from
July 29, 2026 12:55
1e508a4 to
3e16767
Compare
JTorreG
approved these changes
Jul 29, 2026
ohad-perets
marked this pull request as ready for review
July 29, 2026 14:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the 5.14 changelog entry and document support for the new operating systems, and unify the RHEL/Rocky Dockerfile partials.
Changelog and specs:
New OS support:
Dockerfile partial unification:
Fixes:
Note: the 5.14 build number and release date are placeholders (5.TBD.0 / TBD) pending the promoted build.
Proposed changes
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩