Skip to content

NLB-6564: Updated NIGNXaaS dataplane change log with version information #632

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

xynicole
Copy link
Contributor

@xynicole xynicole commented May 30, 2025

Proposed changes

Added an additional changelog page for version information, as this page would become very lengthy.

Closes #ISSUE

Checklist

Before merging a pull request, run through this checklist and mark each as complete.

  • I have read the contributing guidelines
  • I have signed the F5 Contributor License Agreement (CLA)
  • I have rebased my branch onto main
  • I have ensured my PR is targeting the main branch and pulling from my branch from my own fork
  • I have ensured that the commit messages adhere to Conventional Commits
  • I have ensured that documentation content adheres to the style guide
  • If the change involves potentially sensitive changes1, I have assessed the possible impact
  • If applicable, I have added tests that prove my fix is effective or that my feature works
  • I have ensured that existing tests pass after adding my changes
  • If applicable, I have updated README.md and CHANGELOG.md

Footnotes

  1. Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content.

@xynicole xynicole requested a review from a team as a code owner May 30, 2025 13:52
@xynicole xynicole marked this pull request as draft May 30, 2025 13:52
@github-actions github-actions bot added documentation Improvements or additions to documentation product/nginxaas NGINX as a Service for Azure labels May 30, 2025
Copy link

Deploy Preview will be available once build job completes!

Name Link
😎 Deploy Preview https://frontdoor-test-docs.nginx.com/previews/docs/632/

@xynicole xynicole marked this pull request as ready for review June 5, 2025 17:40
title: "Version Changelog"
weight: 950
toc: true
docs: "DOCS-870" #need to update
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I create a new page for the version changelog or keep the version information on our regular Changelog page?

title: "Version Changelog"
weight: 950
toc: true
docs: "DOCS-870" #need to update
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
docs: "DOCS-870" #need to update

If you don't have the correct number for this doc or need a new one, just remove the line and we will add it automatically at a later date

url: /nginxaas/azure/version-changelog/
---

Learn about the latest versions in F5 NGINX as a Service for Azure.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Learn about the latest versions in F5 NGINX as a Service for Azure.
Learn about the latest versions of F5 NGINX as a Service for Azure.

@ryepup
Copy link

ryepup commented Jun 6, 2025

this content looks fine to me, there's some debate in slack on whether to put in the normal changelog or have a different page. I'm fine either way.

In the very, very, very long run, this might be something to automate; our CI pipelines that deploy these dataplane images could publish the version data somewhere and a bot opens a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation product/nginxaas NGINX as a Service for Azure
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants