[docs-scanner] GitHub Cache API v2 migration framed as future when already completed

[docker-agent]

File: content/manuals/build/ci/github-actions/cache.md

Issue

The documentation frames the GitHub Cache service API v2 migration as something that "will be" required, when the transition has already been completed:

Starting April 15th, 2025, only GitHub Cache service API v2 will be supported.

The date April 15th, 2025 is in the past (this scan is running in 2026), yet the documentation still uses future-tense framing ("will be supported") and presents this as an upcoming change rather than a completed transition.

Why this matters

Readers following this documentation in 2026 will be confused by the temporal framing. The text suggests they need to prepare for a future migration that has already happened. This creates uncertainty about whether the information is current and whether they need to take action.

The important note section that follows also uses present-tense language ("You're probably using outdated tools") which contradicts the future-tense framing of the migration date, adding to the confusion.

Suggested fix

Reframe the section to reflect that this is a completed migration:

As of April 15th, 2025, only GitHub Cache service API v2 is supported. The legacy v1 API has been shut down.

Update the error message context to reflect that users encountering this error are using outdated tools that don't support the current API version, not tools that need to be prepared for a future change.

---

Found by nightly documentation quality scanner