feat(adapters): widen @relayfile/sdk peer range across all adapters#23
Merged
khaliqgant merged 3 commits intomainfrom Apr 21, 2026
Merged
feat(adapters): widen @relayfile/sdk peer range across all adapters#23khaliqgant merged 3 commits intomainfrom
khaliqgant merged 3 commits intomainfrom
Conversation
Consumers (sage, cloud, nightcto, msd) are bumping @relayfile/sdk to ^0.3.0 for contentIdentity support. Adapters' pinned ^0.1.7 declaration forced npm overrides in every consumer as a workaround. Changes: - github: widen existing peerDependencies from ^0.1.7 to >=0.1.7 <1 - linear, notion, slack, gitlab, teams: move @relayfile/sdk from dependencies to peerDependencies (with the same widened range) so adapters use the consumer's chosen SDK rather than pulling a nested 0.1.x copy. Added @relayfile/sdk: ^0.3.1 to each adapter's devDependencies so typecheck + test keep working in CI. - All six adapters bumped by one patch (0.1.6→0.1.7 or 0.1.7→0.1.8). No runtime code changes. Pure packaging update. After merge + publish, consumers can drop their overrides blocks: - sage: #89 overrides block - cloud: (none added yet) - nightcto: (none added yet) - msd: (none added yet) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Previous commit ignored the entire .claude/ directory, which is too broad — skills, commands, and other shared config belong in the repo. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Addresses Devin review comment on #23: github's devDependency on @relayfile/sdk was left at ^0.1.7 while every other adapter got bumped to ^0.3.1, leaving github building/testing against stale SDK types. Also widens @relayfile/adapter-core's peer range (and devDep) — core is depended on by github, and its pinned ^0.1.7 peer forced a nested @relayfile/sdk@0.1.7 install that conflicted with github's own nested 0.3.x, producing "two identities for RelayFileClient" type errors. Now all six adapters + core dedupe on @relayfile/sdk@0.3.2. adapter-core bumped 0.1.6 → 0.1.7. Co-Authored-By: Claude Opus 4.7 (1M context) <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
1 participant
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
Unblocks consumers (sage, cloud, nightcto, MSD) that are bumping `@relayfile/sdk` to `^0.3.0` for contentIdentity support. Without this PR, each consumer has to add an `overrides` block to their `package.json` because adapters pin SDK at `^0.1.7` (either via peerDependencies or nested dependencies).
Changes
No runtime code changes. Pure packaging update.
Why patch bumps (not minor)
Strictly speaking, converting a regular dep to a peer dep is a breaking change since consumers who relied on auto-install now need to install `@relayfile/sdk` themselves. In practice, every known consumer already declares `@relayfile/sdk` at the top level (sage, cloud, nightcto, MSD, relayfile itself), so this is behaviorally no-op for them. Going with patch to keep the churn minimal — happy to re-cut as minors if you'd rather.
Publish
After merge, publish all six updated packages via whatever workflow_dispatch you use. Consumers can then:
Test plan
Related: