Update changelog.md#456

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Open

achawla2012 wants to merge3 commits intonginx:main

base:main

Choose a base branch

fromachawla2012:patch-3

Open

Update changelog.md#456

achawla2012 wants to merge3 commits intonginx:mainfromachawla2012:patch-3

Conversation

Copy link

Contributor

achawla2012 commentedApr 25, 2025•
edited by mjang
Loading

Projected release: April 30, 2025

Proposed changes

Problem: NGINX One is intaking metrics from customer's data planes that can indicate large negative outcomes that must have action taken on them urgently. Such as , NGINX One checks for CVE impacts. All of this information is extremely valuable, but only if the customer is aware of it in a timely enough fashion to take action.

Solution: If user's data-path has impacting CVEs, we proactively notify, so that use can take action to remedy.

Testing: User registers instance in F5 NGINX One console, and is alerted on CVEs impacting instances.

Please focus on (optional):
Please help editing wording.

Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.

If this PR addresses anissue on GitHub, ensure that you link to it here:

Closes #ISSUE

Checklist

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

I have read thecontributing guidelines
I have signed theF5 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 toConventional Commits
I have ensured that documentation content adheres tothe style guide
If the change involves potentially sensitive changes¹, 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 updatedREADME.md andCHANGELOG.md

Footnotes

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

Update changelog.md

abc720d

achawla2012 requested a review froma team as acode owner

April 25, 2025 18:10

Copy link

github-actionsbot commentedApr 25, 2025•
edited
Loading

🎉 Thank you for your contribution! It appears you have not yet signed theF5 Contributor License Agreement (CLA), which is required for your changes to be incorporated into an F5 Open Source Software (OSS) project. Please kindly read theF5 CLA and reply on a new comment with the following text to agree:

I have hereby read the F5 CLA and agree to its terms

1 out of2 committers have signed the CLA.
✅ (mjang)[https://github.com/mjang]
❌@achawla2012
_{You can retrigger this bot by commentingrecheck in this Pull Request.}_{Posted by theCLA Assistant Lite bot.}