build: focus Dependabot on security updates - #1929
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The required path-filtered check would block unrelated PRs, and fork validation needs secure credential handling.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Stops routine Dependabot updates while adding CFS validation for dependency PRs.
Changes:
- Removes scheduled npm and GitHub Actions updates.
- Adds Azure PR triggers for npm manifest changes.
File summaries
| File | Description |
|---|---|
.github/dependabot.yml |
Removes scheduled version updates. |
.azure-pipelines/vscode-java-test-ci.yml |
Adds CFS-backed dependency PR validation. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 2
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
ADO CFS validation is now active through The first run, build 32033309, is attached to this PR as the |
Summary
.github/dependabot.ymlbecause its scheduled npm and GitHub Actions entries create frequent routine version-update pull requests that are not security-drivenmainthat modify npm or Maven dependency inputs used by the CI buildWhy
The repository does not need frequent non-security dependency bump pull requests. The removed configuration scheduled those routine updates; it is not what enables Dependabot security updates.
Security updates can still open immediately when an alert has an available fix. Dependabot cooldown does not delay those updates, as demonstrated by #1923, so CFS availability needs to be enforced separately rather than through the scheduled Dependabot configuration.
Scope
The ADO PR trigger covers
package.json,package-lock.json, Java extension POM files, the Maven wrapper distribution configuration, and the Maven coordinates resolved byscripts/buildJdtlsExt.js. Unrelated pull requests do not consume the CFS validation pipeline. The check is not currently required formain.CFS validation is configured through the Azure DevOps pipeline
VSCode-Test-Runner-CI-Build.ADO validation
The first validation run, build 32033309, reached the CFS-authenticated
npm installstep and failed becausefast-uri@3.1.7was not present in thevscjavafeed at that time. This was the expected gate behavior and confirmed that the pipeline detects dependency versions not yet available from CFS.