jsr icon indicating copy to clipboard operation
jsr copied to clipboard

Publishing with `npx jsr` seems to be no longer working?

Open fry69 opened this issue 2 months ago • 5 comments

There seem to be problems with publishing packages currently when using the recommended npx jsr publish GitHub workflow that gets shown in the documentation and when setting up a new project to publish.

Yesterday I encountered these two errors when trying to publish via GitHub actions:

error: Failed to get OIDC token: status 503 Service Unavailable, response: 'upstream connect error or disconnect/reset before headers. reset reason: overflow'
Command: /home/runner/.npm/_npx/91d31d47806d2506/node_modules/jsr/.download/v2.3.7/linux/deno publish
CWD: /home/runner/work/or-models/or-models
Output: 
Child process exited with: 1
error: Failed to publish @fry69/[email protected]

Caused by:
    expected value at line 1 column 1
Command: /home/runner/.npm/_npx/91d31d47806d2506/node_modules/jsr/.download/v2.3.7/linux/deno publish
CWD: /home/runner/work/deep-diff/deep-diff
Output: 
Child process exited with: 1

Using deno publish instead works fine:

name: Publish JSR
on:
  push:
    branches:
      - main

jobs:
  publish:
    runs-on: ubuntu-latest

    permissions:
      contents: read
      id-token: write

    steps:
      - name: Checkout repository
        uses: actions/checkout@v4

      - name: Setup Deno
        uses: denoland/setup-deno@v2
        with:
          cache: true

      - name: Publish package
        run: deno publish

fry69 avatar Sep 27 '25 06:09 fry69

Have you tried re-running it after a while?

i checked:

  • registry didn't had any change
  • jsr cli didn't change

So maybe something on GitHub side or momentally down time of the cloud provider

AugustinMauroy avatar Sep 27 '25 14:09 AugustinMauroy

So maybe something on GitHub side or momentally down time of the cloud provider

Maybe. But I tried a few times for about an hour and then decided to switch to using deno publish, that worked instantly. That could of course be coincidence.

fry69 avatar Sep 27 '25 14:09 fry69

That could of course be coincidence.

it's should

AugustinMauroy avatar Sep 27 '25 14:09 AugustinMauroy

It did not feel or look like a coincidence though. I hammered that "Retry failed workflow" button until I noticed that Fresh uses deno deploy instead. I copied that and poof it worked.

fry69 avatar Sep 27 '25 14:09 fry69

Well, I created a dummy repo for testing and the npx jsr publish seems to work again, see here -> https://github.com/fry69/jsr-dummy

Feel free to close, but I'd keep it open for others, in case that happens again. It was quite a confusing experience.

fry69 avatar Sep 27 '25 14:09 fry69