build(release): reference workspace members through the workspace protocol

1504 hand-written ranges pointing at workspace members become workspace:^, so
pnpm pack substitutes each member's real version at publication: sibling
peerDependencies follow the family version instead of being pinned at ^0.0.1,
and a reference to a vendored package follows that package's own line. Without
this, publishing 0.0.2 ships peer ranges naming a version that does not exist,
and 0.0.1-rc.1 does not satisfy ^0.0.1 either.

It also retires ranges that had gone stale against the workspace: ^4.0.0-rc.6
for a 4.0.0-rc.7 checkout, ^3.17.0 for schemastery 3.18.0.

workspace:* stays where an exact published version is the point, which is how
the Landlock entry pins its platform packages.

A workspace constraint now requires the protocol, so a new package cannot
reintroduce a hand-written range. The same constraint caught packages/boot/cmdline
arriving on master without the publishable trio, which this change completes.
This commit is contained in:
imccyu
2026-08-11 00:17:09 +08:00
parent d4128ae57f
commit 2c85c484d3
218 changed files with 1774 additions and 1736 deletions
+2 -2
View File
@@ -30,9 +30,9 @@
"author": "Shigma <shigma10826@gmail.com>",
"license": "MIT",
"peerDependencies": {
"@deepseek-ai/cordis": "^4.0.0-rc.7"
"@deepseek-ai/cordis": "workspace:^"
},
"dependencies": {
"@deepseek-ai/cosmokit": "^1.8.1"
"@deepseek-ai/cosmokit": "workspace:^"
}
}