Promote the DockerfileComponentDetector to default#1820
Conversation
|
👋 Hi! It looks like you modified some files in the
If none of the above scenarios apply, feel free to ignore this comment 🙂 |
There was a problem hiding this comment.
Pull request overview
This PR promotes the Dockerfile detector from experimental to a standard/default detector, meaning its results will now be included in scan outputs by default (without requiring an explicit --DetectorArgs ...=Enable opt-in).
Changes:
- Removed
IExperimentalDetectorfromDockerfileComponentDetector, making it a non-experimental detector in orchestrator processing. - Updated Dockerfile detector documentation to remove experimental/opt-in guidance.
Show a summary per file
| File | Description |
|---|---|
| src/Microsoft.ComponentDetection.Detectors/dockerfile/DockerfileComponentDetector.cs | Drops the experimental marker interface so the orchestrator includes Dockerfile detector output by default. |
| docs/detectors/dockerfile.md | Removes experimental status and opt-in instructions/limitations now that the detector is promoted. |
Copilot's findings
- Files reviewed: 2/2 changed files
- Comments generated: 0
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1820 +/- ##
============================
============================
☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
No description provided.