Fix README images + breaking change links (Framework, by @loic-sharma).
This item comes from the official release notes, which list pull-request titles. Boring Doc shows the title and classifies it heuristically; open the pull request for the full description.
- Who is affected
- Applications and packages relying on the previous behaviour or signature.
- Practical impact
- Behaviour or API differences that can break builds or change runtime behaviour.
- What action should I take?
- Review the linked source, update affected code and run your test suite before upgrading.
Official release note·Heuristic classification (50%)
PR title mentions 'breaking' but the change is not in the official breaking-changes index; needs review.
An official announcement or migration guide documents an intended behaviour or API change. A verified source change (git diff) shows code changed but does not by itself prove a public API is breaking. AI interpretations are labelled and never used to classify a change.
- Source commit
- b3045439b7c0
- Source last updated
- Oct 21, 2026
- Last synchronized
- Oct 21, 2026
- Publication status
- needs-review
Publication history
- Oct 21, 2026, 8:31 PM: new → needs-review (ingestion) — High-impact classification (breaking) with confidence 0.50 needs human review.
AI explanationAI-generated · grounded in cited sources
AI explanations are not configured
Set
AI_PROVIDER (for example to openai-compatible with a local Ollama or LM Studio endpoint) to enable grounded explanations. Everything else on this page works without an AI provider.Was this useful?