chore: re-release browser pool profile change as 0.72.0#134
Merged
Conversation
The browser pool profile change (#2484) shipped as 0.71.1 (patch) by mistake; re-releasing under a correct minor version. Release-As: 0.72.0 BREAKING CHANGE: browser pool `profile` is now `BrowserPoolProfile` (id/name only); `save_changes` is no longer accepted on pool profiles. Wire-compatible for inline callers; typed callers must update. Sending `save_changes` on a pool used to return `400` and is now silently ignored.
chruffins
approved these changes
Jun 26, 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.
Re-releases the browser pool profile change (#2484) under a correct minor version.
It shipped as
0.71.1(a patch) by mistake during the release-PR re-sync — a breaking change to the pool profile type (BrowserPoolProfile,save_changesremoved).0.71.1is immutable on npm, so this cuts a proper0.72.0on top via aRelease-Asmarker so release-please opens arelease: 0.72.0PR.Merge with rebase or squash (footers below are preserved either way). After this merges → release-please opens
release: 0.72.0→ merging that publishes@onkernel/sdk@0.72.0+ tagsv0.72.0. Thennpm deprecate @onkernel/sdk@0.71.1.Release-As: 0.72.0
BREAKING CHANGE: browser pool
profileis nowBrowserPoolProfile(id/name only);save_changesis no longer accepted on pool profiles. Wire-compatible for inline callers; typed callers must update. Sendingsave_changeson a pool used to return400and is now silently ignored.