chore(ci): flip Remy to PR against master - #893
Draft
rrama wants to merge 1 commit into
Draft
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Contributor
Code Coverage
|
This was referenced Sep 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds
open-source-agentic-fix-base-branch: masterto.circleci/config.yml'sprodsec/security_scansstep (prodsec-orb v1.2.32), so the agentic-fix bot targetsmasterinstead of whatever feature branch it happens to scan. Same fix as snyk/snyk-ls#1432, opened here as a test to see if it would actually cause a fix PR to land againstmaster.Result: inconclusive, not a failure. Checked the CircleCI
security-scansjob for this PR's commit (pipeline #2165, job 4261). The Open Source scan step ran, but theAgentic fix for blocking Open Source vulnerabilitiesstep logged:There's currently no High-or-above OSS vulnerability on this branch, so the agentic-fix path never engaged — the new
open-source-agentic-fix-base-branchparameter was never exercised, in either direction. This isn't evidence the config change doesn't work; there was simply nothing for it to fix. (The "Configured mode=auto ... Changing to mode=gate" log line is a separate, unrelated mechanism — it governs whether the scan itself blocks the build on this non-release branch, not whether the agentic-fix step runs.)To actually validate this, we'd need either a real High+ vulnerability present when the job runs, or to wait for the next scan that finds one on a branch with this config.
Checklist
Screenshots / GIFs
Visuals that may help the reviewer. Please add screenshots for any UI change. GIFs are most welcome!