Skip to content

fix(ci): rewrite probe — scrape .gdn/i/ dirs, fix broken cache SHA, dispatch breach monitor#224

Merged
DimaBir merged 4 commits intomainfrom
feat/msdo-breach-monitor
Mar 23, 2026
Merged

fix(ci): rewrite probe — scrape .gdn/i/ dirs, fix broken cache SHA, dispatch breach monitor#224
DimaBir merged 4 commits intomainfrom
feat/msdo-breach-monitor

Conversation

@DimaBir
Copy link
Collaborator

@DimaBir DimaBir commented Mar 23, 2026

Summary

  • Rewrites toolchain version probe to scrape MSDO's actual install dirs (.gdn/i/{type}/{pkg}.{version}/) instead of parsing .gdntool XML — simpler, no fragile XML parsing, works with the real MSDO install side effect
  • Removes broken actions/cache@1bd1e32a... SHA that caused the probe to fail on set-up (SHA doesn't exist)
  • Probe now dispatches the breach monitor after committing fresh versions, removing the schedule race condition
  • Breach monitor prompt rewritten with explicit API endpoints, 7-day recency window, ongoing-always-flag rule, repo archival check, and per-ecosystem advisory queries — addresses all gaps found in first run (noop despite active Trivy incident)

Why the previous run failed

actions/cache@1bd1e32a3bdc45362d1e726936510720a7c6158d is not a valid SHA — the action set-up step errored immediately. Correct SHA for v4.2.2 is d4323d4df104b026a6aa633fdb11d772146be0bf, but the approach was rearchitected away from caching entirely.

Test plan

  • Trigger probe manually after merge: gh workflow run toolchain-version-probe.yml
  • Verify .github/toolchain-versions.json committed with resolved versions
  • Verify breach monitor dispatched automatically and reads pinned versions in Step 0

@DimaBir DimaBir requested a review from a team as a code owner March 23, 2026 09:12
Signed-off-by: Dima Birenbaum <dvlasenko86@gmail.com>
@DimaBir DimaBir self-assigned this Mar 23, 2026
@DimaBir DimaBir merged commit dabaaf6 into main Mar 23, 2026
14 of 15 checks passed
@DimaBir DimaBir deleted the feat/msdo-breach-monitor branch March 23, 2026 10:35
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.

2 participants