fix(react): use semantic-release-pnpm to resolve workspace deps on publish#2023
Merged
harbournick merged 1 commit intomainfrom Feb 13, 2026
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes a critical publishing issue in the @superdoc-dev/react package by switching from @semantic-release/npm to semantic-release-pnpm for the release process. The previous plugin (@semantic-release/npm) uses npm publish, which does not resolve pnpm workspace protocols, causing version 1.0.0-canary.2 to be published with the literal string "superdoc": "workspace:*" instead of a concrete version number. This broke installations for consumers. The semantic-release-pnpm plugin properly resolves workspace protocols during publish.
Changes:
- Replace
@semantic-release/npmwithsemantic-release-pnpmin the react package release configuration - Align react package release configuration with the superdoc package (which already uses semantic-release-pnpm)
- Prevent future releases from shipping with unresolved workspace protocols
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
tupizz
force-pushed
the
tadeu/sd-1908-superdoc-devreact-latest-has-invalid-dependency-spec
branch
from
d3792b3 to
5f110eb
Compare
…blish (SD-1908) The react package was using @semantic-release/npm which runs `npm publish` and does not resolve pnpm workspace:* references. This caused version 1.0.0-canary.2 to be published with "superdoc": "workspace:*" as a dependency, breaking npm installs for consumers. Switch to semantic-release-pnpm (already used by the superdoc package) which runs `pnpm publish` and properly resolves workspace:* to actual version numbers before publishing.
tupizz
force-pushed
the
tadeu/sd-1908-superdoc-devreact-latest-has-invalid-dependency-spec
branch
from
419e7d4 to
a4c8ff0
Compare
harbournick
deleted the
tadeu/sd-1908-superdoc-devreact-latest-has-invalid-dependency-spec
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@superdoc-dev/reactrelease config from@semantic-release/npmtosemantic-release-pnpm(already used by thesuperdocpackage)@semantic-release/npmrunsnpm publishwhich does not resolve pnpmworkspace:*references — this caused v1.0.0-canary.2 to ship with"superdoc": "workspace:*", breakingnpm installfor consumerssemantic-release-pnpmrunspnpm publishwhich properly resolves workspace protocols to actual version numbersCloses SD-1908
Test plan
semantic-release-pnpmis already a root dependency (it is — used by superdoc)@latestdist-tag to point to a working version