Release @onkernel/browser-loop v0.12.1 - #95
Merged
Conversation
rgarcia
approved these changes
Sep 4, 2026
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
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/browser-loopto0.12.1and adds the changelog entry for Relax @onkernel/sdk peer version pin to a caret range #94 (relaxing the@onkernel/sdkdependency from an exact pin to>=0.49.0 <1.0.0).Release v0.12.0commit).browser-loop/v0.12.1tag to trigger the publish workflow.Test plan
npm run check:lockfilenpm run typecheck(workspace@onkernel/browser-loop)Note
Low Risk
Release-only version and changelog updates with no application code changes; the SDK range widening was handled in a prior PR.
Overview
Release
@onkernel/browser-loopv0.12.1 — version bump inpackage.jsonandpackage-lock.json, plus a changelog entry for the already-landed dependency change from #94.The 0.12.1 note documents relaxing
@onkernel/sdkfrom an exact pin to>=0.49.0 <1.0.0, so consumers can use compatible SDK minors without waiting on a browser-loop release. No runtime or API code changes in this diff; merging is intended to be followed by taggingbrowser-loop/v0.12.1to publish.Reviewed by Cursor Bugbot for commit 796161e. Bugbot is set up for automated code reviews on this repo. Configure here.