Deno JSR "Could not find version that matches" in CI
Deno resolved a jsr: package but no published version satisfies the requested constraint. The registry has the package, but not a release in the range you asked for.
What this error means
The run fails with "error: Could not find version of \"@scope/pkg\" that matches specified version constraint \"^1.2.0\"".
deno
error: Could not find version of "@std/assert" that matches specified version constraint "^99.0.0"
at file:///home/runner/work/app/app/src/main.ts:1:24Common causes
The constraint has no published release
You requested a range like ^99.0.0 that JSR has never published, so resolution finds nothing to install.
A stale lockfile references a yanked or absent version
The lockfile pins a version no longer available, and CI cannot re-resolve it against the constraint.
How to fix it
Pin a version that exists on JSR
- Check the published versions for the package on JSR.
- Update the specifier or import map to a real version range.
- Re-run so resolution succeeds.
src/main.ts
import { assertEquals } from "jsr:@std/assert@^1.0.0";Refresh the lockfile
Regenerate the lockfile so it reflects versions that currently exist, then commit it.
Terminal
deno cache --reload main.tsHow to prevent it
- Use version ranges that JSR actually publishes.
- Commit an up-to-date deno.lock so CI resolves deterministically.
- Update pins when a dependency version is yanked.
Related guides
Deno npm: specifier "npm package not found" in CIFix Deno "error: npm package ... not found" in CI - an npm: specifier named a package or version the npm regi…
Deno "Failed reading lock file" / integrity mismatch in CIFix Deno lockfile errors in CI - "error: Failed reading lock file" or a deno.lock integrity mismatch when the…
Deno "Relative import path not prefixed with / or ./ or ../" in CIFix Deno "error: Relative import path ... not prefixed with / or ./ or ../" in CI - a bare specifier was used…