Skip to content

CI: pnpm install fails on @jsr/creit-tech__stellar-wallets-kit returning 404 #187

Description

@Benjtalkshow

Bug: CI pnpm install --frozen-lockfile fails with 404 from JSR registry

Symptom

The build-and-lint CI job fails at the Install dependencies step with a 404 error fetching @jsr/creit-tech__stellar-wallets-kit from https://npm.jsr.io. This blocks every PR from passing CI regardless of whether the change touches anything related to wallet kit.

Root cause hypothesis

Two likely explanations:

  • The package was unpublished from JSR (or the version pinned in pnpm-lock.yaml was removed)
  • The CI environment needs JSR registry auth configured (.npmrc token for @jsr scope)

The package is referenced in package.json as:

"@creit-tech/stellar-wallets-kit": "npm:@jsr/creit-tech__stellar-wallets-kit@^2.0.1"

Investigation steps

  • Confirm the package's status on https://jsr.io/@creit-tech/stellar-wallets-kit (does the version still exist?)
  • Check whether https://npm.jsr.io/@jsr/creit-tech__stellar-wallets-kit/-/creit-tech__stellar-wallets-kit-2.0.1.tgz is fetchable with no auth
  • Inspect the CI logs for the exact failing URL (it should be in the pnpm install --frozen-lockfile output)
  • Try pnpm install locally with a clean store to confirm whether it's CI-specific

Possible fixes

  • If the package was unpublished: pin to a published version, switch to a different stellar wallets kit, or vendor it
  • If it's an auth issue: add .npmrc config to the CI workflow that registers the JSR scope, e.g.:
    @jsr:registry=https://npm.jsr.io
    
  • If it's transient: retry the install in CI

Files affected

  • .github/workflows/ci.yml
  • package.json
  • pnpm-lock.yaml (likely needs regeneration once the registry issue is resolved)

Acceptance Criteria

  • pnpm install --frozen-lockfile succeeds in CI from a clean checkout
  • Root cause documented in the issue (unpublished vs auth vs other)
  • PRs that don't touch wallet code are no longer blocked by this install failure
  • If a workaround was applied (e.g. fork/vendor), follow-up tracked separately

Additional notes

This was first surfaced by a contributor on PR #172. Several other PRs (#176, #177, #178, etc.) have been failing CI for the same reason, so unblocking this is a force-multiplier.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions