Relax @onkernel/sdk peer version pin to a caret range - #94
Merged
Conversation
Allows consumers to install a newer @onkernel/sdk without npm resolving two conflicting copies in the same tree.
1 task
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 571673a. Configure here.
Caret ranges on a 0.x version only allow patch bumps, so ^0.49.0 still shadowed newer published SDK versions and didn't fix the mismatch the pin relaxation was meant to solve.
rgarcia
approved these changes
Sep 4, 2026
Contributor
Author
|
tested locally and discussed with @rgarcia |
2 tasks
dprevoznik
added a commit
to kernel/docs
that referenced
this pull request
Sep 4, 2026
browser-loop's exact @onkernel/sdk pin is relaxed to a caret range (kernel/browser-loop#94), matching the same removal already done for the Playwright/computer-use fallback cookbook (#548).
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
@onkernel/sdkwas pinned to an exact0.49.0inpackages/browser-loop/package.json, which forces npm to hoist a second, mismatched copy whenever a consumer's project needs a newer SDK version elsewhere in the tree, producing incompatibleKERNELclient types.^0.49.0so a compatible newer SDK version can be installed and deduped instead of shadowed.Test plan
npm run typecheck(workspace@onkernel/browser-loop) passesnpm test(workspace@onkernel/browser-loop) — same single pre-existing failure as onmain(requires adistbuild, unrelated to this change), no new failuresNote
Low Risk
Dependency-range-only change in one package; no runtime or API logic changes, with typecheck/tests reported passing aside from a pre-existing dist-related test failure.
Overview
@onkernel/browser-loopno longer pins@onkernel/sdkto exactly0.49.0. The dependency is now>=0.49.0 <1.0.0, so installs can resolve a single compatible 0.x SDK across the tree instead of pulling a duplicate copy when the host app uses a newer SDK.package-lock.jsonis updated to match the relaxed range.Reviewed by Cursor Bugbot for commit 6d9eb10. Bugbot is set up for automated code reviews on this repo. Configure here.