multipublish

multipublish

Publishes monorepo packages to multiple registries in a single step. Reads released package info from changesets and loops over configured platforms.

Setup

{
  "$schema": "./node_modules/@stephansama/multipublish/config/schema.json",
  "platforms": [
    ["jsr", { "experimentalGenerateJSR": true }],
    ["npm", { "tokenEnvironmentKey": "NODE_AUTH_TOKEN" }]
  ]
}

Place as .multipublishrc.json, .config/multipublishrc.json, or a multipublish key in package.json. See cosmiconfig docs for all supported filenames.

Core Patterns

Changeset-based release (GitHub Actions)

- name: Create Changeset Release
  uses: changesets/action@v1
  id: changesets
  with:
    publish: pnpm run publish

- name: Publish to other registries
  if: steps.changesets.outputs.published == 'true'
  run: echo "${{ steps.changesets.outputs.publishedPackages }}" | multipublish

changeset publish output is piped into multipublish via stdin. The JSON array of published packages tells multipublish which packages to process and at which versions.

Use --useChangesetStatus instead of stdin

{
  "scripts": {
    "preversion": "multipublish --useChangesetStatus --versionJsr",
    "version": "changeset version"
  }
}

--useChangesetStatus reads which packages have pending (unreleased) changesets directly from the changeset state — without piping from changeset publish. Use it in preversion to update JSR config versions before the changeset version bump runs.

GitHub npm registry with scoped token

{
  "platforms": [
    [
      "npm",
      {
        "registry": "https://npm.pkg.github.com",
        "tokenEnvironmentKey": "GITHUB_TOKEN"
      }
    ]
  ]
}

Set packages: write permission in the GitHub Actions workflow.

Dry run

multipublish --dry

Runs the full flow but passes --dry-run to the underlying publish commands. Use to verify config without publishing.

Common Mistakes

CRITICAL No jsr.json/deno.json and experimentalGenerateJSR not enabled