fix(core): inner @relayauth/sdk dep stuck at ^0.1.0 (republish 0.2.1)#24
Merged
khaliqgant merged 1 commit intomainfrom Apr 23, 2026
Merged
fix(core): inner @relayauth/sdk dep stuck at ^0.1.0 (republish 0.2.1)#24khaliqgant merged 1 commit intomainfrom
khaliqgant merged 1 commit intomainfrom
Conversation
@relayauth/core@0.2.0 was published with "@relayauth/sdk": "^0.1.0" in its dependency list — a stale caret range from before the 0.2.x line. npm dutifully installs the latest matching version (0.1.9) into a nested node_modules/@relayauth/core/node_modules/@relayauth/sdk, so downstream consumers end up with both 0.2.0 (top-level) and 0.1.9 (nested under core) at the same time. Nothing routes through the nested copy from cloud today — every cloud package resolves the top-level 0.2.0 directly — but it is dead weight, wasted install size, and a real bug if any future code path reaches @relayauth/sdk via the core re-export. Fix: change the inner dep to "*" to match the pattern used by @relayauth/server and @relayauth/sdk (both of which use "*" for their sibling workspace deps so publish-time version substitution follows the actual workspace). Bump core to 0.2.1 so the fix can be published and picked up. After merge, republish @relayauth/core@0.2.1 and the nested-sdk diamond disappears on next npm install. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
`@relayauth/core@0.2.0` was published with `@relayauth/sdk: "^0.1.0"` as its dep, a stale caret range from the 0.1.x line. Since npm's highest-match of `^0.1.0` is 0.1.9, consumers install a nested `node_modules/@relayauth/core/node_modules/@relayauth/sdk@0.1.9` alongside the top-level 0.2.0.
Spotted when bumping cloud to 0.2.0 (see AgentWorkforce/cloud#285) — confirmed not routed-through in cloud, but it's dead weight + a real footgun for any future core re-export of the SDK.
Fix
After merge
Republish:
```
npm publish -w @relayauth/core
npm view @relayauth/core@0.2.1
```
On next `npm install` in any downstream consumer, the nested-sdk diamond disappears.
Test plan
🤖 Generated with Claude Code