Deno remote module cache vs CI pipeline: forcing revalidation of unversioned HTTPS imports without --reload wiping everything
Integration boundary A Deno service imports a handful of remote modules over plain HTTPS URLs (not a versioned registry like deno.land/x with @ tags). Locally and in CI, Deno caches these downloads under DENO_DIR keyed by URL, so once a URL is fetched it is not requested again on later runs. The upstream occasionally publishes fixes at the same URL, and the