Copilot Chat asserts that a dependency's client retries failed calls automatically. The project pins an older release of that dependency. How should the developer validate the claim?
- A.
Search the dependency's current documentation, since a client library's retry behaviour is settled early and rarely changes between releases, so the latest description will apply to the pinned release too.
- B.
Check the documentation for the pinned release, and confirm the behaviour with a small test against the version the project actually resolves.
- C.
Ask Copilot Chat to cite the source of its claim and accept the answer if a plausible link is produced.
- D.
Raise an issue with the dependency's maintainers asking them to confirm the behaviour before the change is merged.
Show answer
Answer: B
Validate against the pinned version, and prove it with a test rather than a document.
- A. It assumes stability across releases, which is the assumption under test and the usual cause of this class of defect.
- B. Version-specific documentation plus a probe test settles both the release question and any conditional behaviour.
- C. A requested citation is generated too, and a plausible link is not evidence that it supports the claim.
- D. Maintainers are a slow channel for a question the developer can answer in minutes against the resolved version.