Skip to content

v0.8.0 — opt-in known issues for KB lookups

Choose a tag to compare

@jonnybottles jonnybottles released this 11 Jul 23:56
· 11 commits to main since this release
9361d36

What's new

msrc_search KB lookups (single kb="5094126" or batched kb=[...]) accept a new opt-in parameter, include_known_issues=True, returning the issues Microsoft has publicly confirmed each update introduces — title, symptoms, workaround, and the resolving KB when stated, plus the source URL — best-effort from the KB's public support.microsoft.com page (no credentials, keeping the project's no-API-keys promise).

  • Honest per-KB status: published / none_published (Microsoft publishes no known-issues data for that KB — the norm outside Windows OS updates) / unavailable (retrieval or parse failure — never conflated with "no issues").
  • Landing pages are verified against the requested KB (URL slug or title) so Microsoft's fuzzy /help/{kb} resolver can never attribute another update's issues.
  • Also attaches to not_found KB results, since preview-only updates publish known issues without being MSRC security entries.
  • Bounded reads (MCP_KNOWN_ISSUES_MAX_RESPONSE_BYTES, 4 MiB default), 6 h in-process cache, semaphore-bounded fetches.
  • Default JSON output is unchanged — the block only exists when requested.

Full details in #17.