NGINXaaS for Azure: Update docs for NGINX Plus 37.0.4 stable upgrade - #2209
Draft
kafeelhasan wants to merge 2 commits into
Draft
NGINXaaS for Azure: Update docs for NGINX Plus 37.0.4 stable upgrade#2209kafeelhasan wants to merge 2 commits into
kafeelhasan wants to merge 2 commits into
Conversation
github-actions
Bot
added
documentation
kafeelhasan
marked this pull request as draft
August 14, 2026 09:48
✅ Deploy Preview will be available once build job completes!
|
JTorreG
approved these changes
Aug 14, 2026
y82
approved these changes
Aug 14, 2026
russokj
approved these changes
Aug 14, 2026
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
5 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.
Proposed changes
Update NGINXaaS changelog with R37 release stable channel.
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. ↩