fix(plugins): publish the plugin SDK under the @getpaseo scope

jb/paseo

The daemon imports the plugin SDK at runtime, but the workspace was named
@paseo/plugin and marked private, so it was never published. 0.5.0-beta.1
shipped @getpaseo/server depending on a package that does not exist and
`npm install @getpaseo/cli@beta` failed with a 404 for every user.

Two things hid it. sync-workspace-versions only rewrites deps matching
@getpaseo/*, so the "*" range on @paseo/plugin survived untouched into the
published tarball. And `npm pack --dry-run`, which is all release:check and
CI run, lists files without ever resolving the dependency graph.

Renaming to @getpaseo/plugin rather than publishing the old name: @paseo is
not our scope on npm, so that name could never have been published at all.
The rename also brings the package under the version-sync filter, which is
what pins it correctly from here on.

Plugins scaffolded against the old name still import @paseo/plugin. Both
spellings resolve through plugin-sdk-specifiers.ts, tagged COMPAT with a
removal date, so existing plugins keep loading.

This does not repair 0.5.0-beta.1 — a published tarball's dependencies
cannot be changed. The package publishes with the next release.

This commit is contained in:

Mohamed Boudra

2026-08-19 15:52:51 +02:00

parent ce905d9483

commit 929d2b717e

42 changed files with 216 additions and 188 deletions

									
										docs/release.md
									
		+1
		-1
	
												View File
												
				@@ -120,7 +120,7 @@ republish the packages:

				```bash

				PASEO_VERSION=$(node -p "require('./package.json').version")

				for package in highlight relay protocol client server cli; do

				for package in highlight relay protocol client plugin server cli; do

				  npm dist-tag add "@getpaseo/$package@$PASEO_VERSION" beta

				done

				```