v0.7.1 — Fix workspace:* leak in published tarballs
Fixed
-
Broken 0.7.0 release: All
@logtide/*@0.7.0packages were published with literalworkspace:*specifiers in theirdependencies, causingERR_PNPM_WORKSPACE_PKG_NOT_FOUNDonpnpm addand equivalent failures on npm. All packages have been republished as0.7.1with proper version specifiers.Fixes logtide-dev/logtide#189.
Changed
- CI hardening:
publish.ymlnow fails fast if anypackage.jsonstill contains theworkspace:protocol after the version-rewrite step, preventing future broken releases. - CI completeness:
publish.ymlnow also publishes@logtide/browserand@logtide/cli, which were previously missing from the publish job.
Upgrade
# pnpm
pnpm add @logtide/sveltekit@0.7.1
pnpm add @logtide/nextjs@0.7.1
pnpm add @logtide/nuxt@0.7.1
# ... etc.
# npm
npm install @logtide/sveltekit@0.7.1Affected packages
| Package | Version |
|---|---|
| @logtide/types | 0.7.1 |
| @logtide/core | 0.7.1 |
| @logtide/browser | 0.7.1 |
| @logtide/sdk-node | 0.7.1 |
| @logtide/express | 0.7.1 |
| @logtide/fastify | 0.7.1 |
| @logtide/nextjs | 0.7.1 |
| @logtide/nuxt | 0.7.1 |
| @logtide/sveltekit | 0.7.1 |
| @logtide/hono | 0.7.1 |
| @logtide/angular | 0.7.1 |
| @logtide/elysia | 0.7.1 |
| @logtide/cli | 0.7.1 |
If you were on 0.7.0 and hit installation errors, upgrade directly to 0.7.1.