chore(release): lock down public release hygiene before changeset PR#2
Closed
pyyush wants to merge 1 commit intofix/e2e-replayfrom
Closed
chore(release): lock down public release hygiene before changeset PR#2pyyush wants to merge 1 commit intofix/e2e-replayfrom
pyyush wants to merge 1 commit intofix/e2e-replayfrom
Conversation
…side-package publish This narrows the public release surface before the follow-up changeset work. The workflow now blocks tracked operator docs/state files, the README banner uses a hosted asset that renders on npm, and integration packages are marked non-publishable with an explicit prepublish failure. Constraint: Keep this as a stacked prep PR on top of fix/e2e-replay without bundling unrelated dirty-worktree edits Rejected: Commit the cleanup from the active dirty worktree directly | risked scooping unrelated uncommitted changes into the PR Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep integration packages private unless they gain a deliberate published-package contract and files allowlist Tested: Root npm ci/build/typecheck/test, browser-use npm ci/typecheck/test, root npm pack --dry-run, integration npm publish --dry-run failure paths Not-tested: Browserbase npm ci on this base branch; package-lock.json is out of sync before this prep change
Owner
Author
|
Closing as redundant. The release-hygiene changes were landed directly onto #1. |
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.
Why
This branch prepares
fix/e2e-replayfor a later changeset PR by tightening the public release surface and preventing internal/operator files from being tracked or published.What changed
.gitignorefor.omx/,.pilot/,.dev-session/, internal docs/plans, and staff-engineer state files.docs/plans/and runtime state directories are caught correctly.privateand added aprepublishOnlyfailure to block accidental publishing.Verification
npm ci && npm run build && npm run typecheck && npm testnpm ci && npm run typecheck && npm testinintegrations/browser-usenpm pack --dry-run --jsonnpm publish --dry-runfails for both integration packages as intendedRisks
integrations/browserbasestill has a pre-existingpackage-lock.jsonmismatch on this base branch, sonpm cithere was not part of this prep PR verification.