Skip to content

Conversation

@attriaayush
Copy link
Contributor

@attriaayush attriaayush commented Dec 19, 2025

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: ___)
  • Includes product update to be announced in the next stable release notes

What does this PR do?

Bumping the necessary packages for SBOM test to the latest. Extending the acceptance test for SBOM test. This change is in preparation for the SBOM Test EA launch in the next release cycle.

@attriaayush attriaayush force-pushed the feat/sbom-test-with-reachability branch 3 times, most recently from 52bda6b to 7123c1d Compare December 19, 2025 13:52
@snyk snyk deleted a comment from github-actions bot Dec 19, 2025
@attriaayush attriaayush force-pushed the feat/sbom-test-with-reachability branch from 7123c1d to 24c43bc Compare December 19, 2025 13:53
@attriaayush attriaayush marked this pull request as ready for review December 19, 2025 13:54
@attriaayush attriaayush requested review from a team as code owners December 19, 2025 13:54
@attriaayush attriaayush force-pushed the feat/sbom-test-with-reachability branch 3 times, most recently from e5d1bf3 to a1072af Compare January 6, 2026 16:15
@attriaayush attriaayush force-pushed the feat/sbom-test-with-reachability branch from a1072af to 4935cd5 Compare January 6, 2026 16:22
@attriaayush attriaayush merged commit 4f28ed4 into main Jan 6, 2026
6 checks passed
@attriaayush attriaayush deleted the feat/sbom-test-with-reachability branch January 6, 2026 19:14
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