You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
vertex-ai-models: Wayback snapshot doesn't match the live feed #83
As a team relying on Google Vertex AI model deprecations, we want vertex-ai-models to store its events even when the Wayback Machine's snapshot lags behind the live feed.
What happens
On 2026-11-18, vertex-ai-models refused to store anything: kit.Cite found that the Wayback snapshot didn't match the live feed. That's the citation check working as designed ("no provenance, no event"), but if the archive keeps serving a stale copy, the plugin reports nothing day after day.
Subtasks
Find out why: the feed changes often (each new release note changes the bytes), or the archive serves an older capture
Decide the fix: compare only the entries the plugin uses rather than the whole feed, retry the snapshot later, or cite the entry's own permalink
Golden test for the chosen behaviour
Acceptance criteria
Two daily runs in a row store Vertex AI deprecations when the feed has new ones
An event is still never stored without a matching citation
Closing as completed: kit.Cite now compares the parsed entries the source uses, not the whole feed, so a new release note on the live feed no longer fails the citation. If the archive ever serves a copy the source cannot read, source health (I22, #250) reports it instead of the source staying silent.
Activity
adssib commentedon Nov 21, 2026
Closing as completed:
kit.Citenow compares the parsed entries the source uses, not the whole feed, so a new release note on the live feed no longer fails the citation. If the archive ever serves a copy the source cannot read, source health (I22, #250) reports it instead of the source staying silent.