JSR analytics now records user agents
Download tracking now captures client user agents for both JSR and npm package fetches, improving analytics detail.
Read the issue →Download tracking now captures client user agents for both JSR and npm package fetches, improving analytics detail.
Read the issue →JSR switches search infrastructure to Algolia, with a follow-up fix to scope filtering and ranking.
Read the issue →JSR tightened provenance verification and auth state handling, added 5% OTLP sampling, and hardened frontend responses.
Read the issue →Stops caching live publish-status and routes package caching by public URL so metadata invalidates correctly after publish.
Read the issue →Adds a reaper for stale publishing tasks so stranded publishes can regenerate package metadata and unblock versions.
Read the issue →Major cache and crawl-control work reduced origin load on docs/diff pages, while API tracing was upgraded to report errors more accurately and export logs.
Read the issue →A DB-first Worker cutover landed, caching was widened, then the cutover was reverted the same day while keeping the DB auth pre-step.
Read the issue →JSR moved read-only stats/metrics into workers-rs, added Hyperdrive Postgres connectivity, and began proxying all other paths to compute.
Read the issue →Big infrastructure refactor plus telemetry changes, with several frontend accessibility and usability fixes and a few important backend corrections.
Read the issue →The API now adds CDN caching for user, sitemap, package manifest, and publish flows, cutting load on frequently hit unauthenticated endpoints.
Read the issue →JSR migrates its Fresh frontend from Cloud Run to a standalone Cloudflare Worker, with routing and deployment updated for the cutover.
Read the issue →Switched the frontend to Vite/Fresh 2.3 and fixed docs markdown lookup under the new build layout.
Read the issue →A staff-detection bug was corrected and the frontend rate limit was doubled to ease request pressure.
Read the issue →Cloud Run’s frontend path now rate-limits abusive IPs, protecting cache-miss traffic without affecting modules, API, or npm compat.
Read the issue →