Skip to content

Chore/add aibom enrich flag - #7022

Merged
sburuiana-snyk merged 1 commit into
mainfrom
chore/add-aibom-enrich-flag
Jul 27, 2026
Merged

Chore/add aibom enrich flag#7022
sburuiana-snyk merged 1 commit into
mainfrom
chore/add-aibom-enrich-flag

Conversation

@sburuiana-snyk

@sburuiana-snyk sburuiana-snyk commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

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 | Medium | High)
  • Highlights breaking API changes (if applicable)
  • Links to automated tests covering new functionality
  • Includes manual testing instructions (if necessary)
  • Updates relevant GitBook documentation (PR link: here)
  • Includes product update to be announced in the next stable release notes

What does this PR do?

Bumps cli-extension-ai-bom to expose the new --enriched flag on snyk aibom and snyk aibom test, wiring it through to the AI-BOM API as enriched=true.

Changes:

  • Upgrade github.com/snyk/cli-extension-ai-bom to v0.0.0-20260721084000-da8dc26c77f2 in cliv2/go.mod and cliv2-private/go.mod
  • Add an acceptance test asserting snyk aibom --enriched sends enriched=true on the Create AI-BOM request

Where should the reviewer start?

  1. test/jest/acceptance/snyk-aibom/aibom.spec.ts — new test for --enriched flag wiring
  2. cliv2/go.mod — dependency bump (the flag implementation lives in cli-extension-ai-bom)

How should this be manually tested?

make build
./binary-releases/snyk-linux-amd64 aibom test/fixtures/ai-bom/python-chatbot --experimental --enriched
./binary-releases/snyk-linux-amd64 aibom test test/fixtures/ai-bom/python-chatbot --experimental --enriched

@sburuiana-snyk
sburuiana-snyk requested a review from a team as a code owner July 22, 2026 08:30
@snyk-io

snyk-io Bot commented Jul 22, 2026

Copy link
Copy Markdown

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

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@snyk-pr-review-bot

This comment has been minimized.

@sburuiana-snyk
sburuiana-snyk force-pushed the chore/add-aibom-enrich-flag branch 2 times, most recently from ee063cf to b1c1384 Compare July 27, 2026 09:54
@snyk-pr-review-bot

This comment has been minimized.

@snyk-pr-review-bot

This comment has been minimized.

chore: update go mods
@sburuiana-snyk
sburuiana-snyk force-pushed the chore/add-aibom-enrich-flag branch from b1c1384 to fd92b11 Compare July 27, 2026 14:12
@sburuiana-snyk
sburuiana-snyk enabled auto-merge July 27, 2026 14:12
@snyk-pr-review-bot

Copy link
Copy Markdown

PR Reviewer Guide 🔍

🧪 PR contains tests
🔒 No security concerns identified
⚡ No major issues detected
📚 Repository Context Analyzed

This review considered 6 relevant code sections from 6 files (average relevance: 1.00)

🤖 Repository instructions applied (from AGENTS.md)

@sburuiana-snyk
sburuiana-snyk merged commit 52c2366 into main Jul 27, 2026
10 checks passed
@sburuiana-snyk
sburuiana-snyk deleted the chore/add-aibom-enrich-flag branch July 27, 2026 14:56
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.

2 participants