Repository navigation
chore(changeset): launch @e2e-dev/browser-run on a release minor - #1747
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
No issues found across 2 files
Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.
View guided diff | Turn on auto-fix | Re-trigger cubic
okwasniewski
force-pushed
the
oskar/browser-run-minor
branch
from
November 13, 2026 12:35
4dfb456 to
c97494e
Compare
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.
New packages launch on a
**Release:**minor (0.1.0), not patch 0.0.1, since^0.0.xpins exactly. Split out the@e2e-dev/webCDP header patch into its own changeset so the**Release:**summary only covers browser-run.Merge only after
@e2e-dev/browser-run@0.0.0is on npm with a trusted publisher onrelease.ymland a nightly proves OIDC, so #1590 can publish it.