Skip to content

chore: bumps cli-extension-os-flows to combine FF checks into fewer API calls#6883

Open
bsalomon-snyk wants to merge 1 commit into
mainfrom
feat/bump-os-flows-for-batch-ff-checks
Open

chore: bumps cli-extension-os-flows to combine FF checks into fewer API calls#6883
bsalomon-snyk wants to merge 1 commit into
mainfrom
feat/bump-os-flows-for-batch-ff-checks

Conversation

@bsalomon-snyk
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)
  • [N/A] Highlights breaking API changes (if applicable)
  • [N/A] Links to automated tests covering new functionality
  • [N/A] Includes manual testing instructions (if necessary)
  • [N/A] Updates relevant GitBook documentation (PR link: ___)
  • [N/A] Includes product update to be announced in the next stable release notes

What does this PR do?

Bumps cli-extension-os-flows to pick up the latest main:

  • fix: batch feature-flag checks into fewer API calls
  • fix: upgrade golang.org/x/net to v0.55.0
  • fix: tolerate per-project resolution failures in --all-projects orchestrator path

Where should the reviewer start?

cliv2/go.mod

How should this be manually tested?

Manual testing can verify FFs are respected for 'snyk test' and/or 'snyk monitor'.

CI tests/verifying that User Journey tests that require feature-flags to pass, namely:

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

N/A - internal changes

Risk assessment (Low | Medium | High)?

Low - batch FF checks were already employed in some cases. This uses them for all FF checks.

What are the relevant tickets?

https://snyksec.atlassian.net/browse/DGP-1762

…PI calls

  - fix: bump cli-extension-os-flows to batch FF checks into fewer API calls
  - fix: upgrade golang.org/x/net to v0.55.0
  - fix: tolerate per-project resolution failures in --all-projects orchestrator path
@bsalomon-snyk bsalomon-snyk requested a review from a team as a code owner June 4, 2026 20:23
@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Jun 4, 2026

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
Copy link
Copy Markdown

PR Reviewer Guide 🔍

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

This review considered 7 relevant code sections from 3 files (average relevance: 0.94)

🤖 Repository instructions applied (from AGENTS.md)

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 4, 2026

Warnings
⚠️

"chore: bumps cli-extension-os-flows to combine FF checks into fewer API calls" is too long. Keep the first line of your commit message under 72 characters.

Generated by 🚫 dangerJS against b96fe8e

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.

1 participant