Skip to content

Conversation

@pkey
Copy link
Contributor

@pkey pkey commented Jan 27, 2026

Pull Request Submission Checklist

  • Follows CONTRIBUTING guidelines
  • Commit messages are release-note ready, emphasizing what was changed, not how.
  • Includes detailed description of changes
  • Contains risk assessment (Low)
  • Highlights breaking API changes (N/A)
  • Links to automated tests covering new functionality
  • Includes manual testing instructions
  • Updates relevant GitBook documentation (N/A - experimental feature)
  • Includes product update to be announced in the next stable release notes

What does this PR do?

Updates cli-extension-ai-bom to include:

  • New snyk redteam --experimental get --id=<scan-id> command for retrieving scan results
  • Progress UI improvements during red team scans
  • Improved error handling for scan retrieval

Where should the reviewer start?

cliv2/go.mod - the dependency version bump

How should this be manually tested?

  1. Build the CLI: make build
  2. Run a red team scan: snyk redteam --experimental scan --config=config.yaml
  3. Copy the scan ID from the output
  4. Retrieve results: snyk redteam --experimental get --id=<scan-id>

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

Users can now retrieve red team scan results using snyk redteam --experimental get --id=<scan-id>. The scan command also now shows progress during execution.

Risk assessment

Low - This is a dependency version bump that adds new experimental functionality.

What are the relevant tickets?

  • AIRT-368: Progress UI
  • AIRT-369: Get results command

@pkey pkey requested review from a team as code owners January 27, 2026 15:44
Updates cli-extension-ai-bom to include:
- New `snyk redteam --experimental get --id=<scan-id>` command
- Progress UI improvements during red team scans
@github-actions
Copy link
Contributor

github-actions bot commented Jan 27, 2026

Warnings
⚠️ There are multiple commits on your branch, please squash them locally before merging!

Generated by 🚫 dangerJS against 8e0c747

@pkey pkey self-assigned this Jan 27, 2026
@PeterSchafer
Copy link
Contributor

@pkey approved but you will need to take another look at the tests :)

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