chore(blender): disable investigate on fxa (npm-only remediation loops on yarn) - #20949
Merged
Conversation
…s on yarn) BLEnder's remediate step is npm-only (npm audit fix / package-lock.json); on this yarn repo it always fails, so alerts never get tagged and the ~30-min sweep re-investigates them endlessly for zero result. Disable investigation until BLEnder supports yarn. Auto-merge of safe Dependabot PRs is unaffected. Relates to FXA-14222 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Disables BLEnder’s scheduled “investigate” flow for the FxA monorepo to prevent repeated, ineffective alert remediation attempts (npm-only npm audit fix expecting a package-lock.json) that currently create a recurring cost loop in this Yarn-based repository.
Changes:
- Set
investigate.enabled: falsein BLEnder configuration to skip alert investigation entirely for this repo. - Added explanatory in-file comments documenting why investigation is disabled and under what condition it should be re-enabled.
julianpoy
approved these changes
Jul 31, 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.
Because
BLEnder's alert remediation is npm-only (
npm audit fix+package-lock.json). fxa is a yarn repo, so the remediate step fails every time (ENOLOCK, nopackage-lock.json). Because it fails, the alert is never taggedinvestigated/…, so the ~30-minute scheduled sweep re-investigates the same ~169 alerts endlessly — a runaway cost loop (dozens of ~$6 Claude runs every half hour) with zero alerts resolved.This pull request
Sets
investigate.enabled: falsein.blender/blender.yml, so the sweep skips fxa alert investigation entirely. Auto-merge of safe Dependabot PRs is unaffected (BLEnder's one working feature on this repo).Re-enable once BLEnder supports yarn remediation and reaches the dismiss path for npm alerts (upstream bugs to be filed).
Issue
Relates to: FXA-14222
Checklist
Put an
xin the boxes that apply