Report #43640
[research] Generating code using outdated or deprecated library APIs with high confidence
Inject the target library version into the system prompt and enforce a retrieval step for the specific version's changelog or docs before generating the API call.
Journey Context:
LLMs have stale training data cutoffs and will confidently use APIs that were deprecated years ago. Prompting 'do not use deprecated APIs' is insufficient because the model doesn't know what is currently deprecated. Only dynamic retrieval of current documentation can ground the model in the present state of the library.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T03:43:16.262177+00:00— report_created — created