Skip to content

feat: update cli-extension-os-flows for Closed Beta. - #6081

Merged
bsalomon-snyk merged 1 commit into
mainfrom
feat/upd-osflows-ext-for-cb
Jul 31, 2025
Merged

feat: update cli-extension-os-flows for Closed Beta.#6081
bsalomon-snyk merged 1 commit into
mainfrom
feat/upd-osflows-ext-for-cb

Conversation

@bsalomon-snyk

Copy link
Copy Markdown
Contributor
  • adds Risk Score to Open Source test if feature flags are present

Pull Request Submission Checklist

  • [x ] Follows CONTRIBUTING guidelines
  • [x ] Commit messages
    are release-note ready, emphasizing
    what was changed, not how.
  • [x ] Includes detailed description of changes
  • [x ] Contains risk assessment (Low | Medium | High)
  • [x ] Highlights breaking API changes (if applicable)
  • [x ] Links to automated tests covering new functionality
  • [x ] Includes manual testing instructions (if necessary)
  • Updates relevant GitBook documentation (PR link: ___)
  • Includes product update to be announced in the next stable release notes

What does this PR do?

Adds risk score to the JSON and human readable CLI output of the Open Source Test for users with these feature flags enabled.

Where should the reviewer start?

Testing that existing features are unaffected. Users opting in to closed beta/testers can verify presence of risk score on test findings.

How should this be manually tested?

Please see documentation at https://docs-preview.snyk.io/9UspT11TEeR92StpZv8B/risk-score-in-cli

What's the product update that needs to be communicated to CLI users?

There are no changes for customers who are not opted in.

Risk assessment (Low | Medium | High)?

Low - closed beta behind feature flags

Any background context you want to provide?

Adds risk score to Open Source Test for select customers

  - adds Risk Score to Open Source test if feature flags are present
@snyk-io

snyk-io Bot commented Jul 31, 2025

Copy link
Copy Markdown

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

code/snyk check is complete. No issues have been found. (View Details)

@bsalomon-snyk
bsalomon-snyk marked this pull request as ready for review July 31, 2025 19:11
@bsalomon-snyk
bsalomon-snyk requested a review from a team as a code owner July 31, 2025 19:11
@PeterSchafer

Copy link
Copy Markdown
Contributor

Suggestion: At some point we might want to add some happy path User Journey tests for Risk score. You might even be able to re-use some of the existing tests in test/jest/acceptance/snyk-test and add the risk score check in for example the --json output

@bsalomon-snyk
bsalomon-snyk merged commit 010f44b into main Jul 31, 2025
9 checks passed
@bsalomon-snyk
bsalomon-snyk deleted the feat/upd-osflows-ext-for-cb branch July 31, 2025 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants