Skip to main content

LATEST_RELEASE_URL

Constant LATEST_RELEASE_URL 

Source
pub const LATEST_RELEASE_URL: &str = "https://github.com/Life-Experimentalist/dev-prune/releases/latest";
Expand description

The release page for the latest published release.

Contacted by devp update and by the interval-gated check behind run/status/init (off via update_check false or DEV_PRUNE_OFFLINE). See the network policy in docs/PRIVACY.md.

Deliberately the website, not api.github.com. GitHub redirects this page to releases/tag/<tag>, and the tag is read out of that Location header without following it — nothing else about the page is needed. The API endpoint that used to answer the same question allows an unauthenticated address sixty requests an hour and answered 403 once a busy laptop had spent them, which made devp update say the network was down when it was not. The website has no per-address quota.

Both resolve the release GitHub has marked latest, which is the newest binary release and nothing else: the extension’s releases are published with make_latest: false precisely so they never surface here. They must not. The tag read from here is fed to compare_versions after a leading v is stripped, and a vscode-v0.4.0 tag arriving here would leave every installed copy unable to compare its own version for as long as that release stayed newest.