GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — ci: release on demand and gate publishing on approval by spicysouvlaki · Pull Request #205 · browserbase/sdk-python

Conversation

@spicysouvlaki

@spicysouvlaki spicysouvlaki commented Nov 4, 2026

Copy link
Copy Markdown
Collaborator

Releases become deliberate (CB-593). Release PRs open only when someone runs Release Please, and the PyPI publish waits for approval in the release environment. Merging this doesn't cut a release.

🤖 Generated with Claude Code

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@spicysouvlaki @claude
ci: release on demand and gate publishing on approval
b3dd0ee
CB-593. Until now, every push to main ran release-please, which kept a
release PR open at all times, and merging it published to PyPI through
the release event with no further check. The 1-pager wants publishing to
be a deliberate, manual step.

- release-please.yml now runs on workflow_dispatch, or on a push that
  changes .release-please-manifest.json (a release PR merging), which
  still tags it and creates the GitHub Release. Ordinary pushes no longer
  open or refresh a release PR. The changed-files check works for any
  merge method; matching on the "release: " title wouldn't.
- The publish job runs in the "release" environment, which requires
  William's approval (created 11-04). Manual re-publishes go through the
  same gate.
- No release-as input: release-please-action ignores it in manifest mode.
  To force a version, land a commit with a "Release-As: x.y.z" footer.

stlc treats .github/workflows/* as branch-owned scaffolding, so these
edits survive regeneration and need no re-seal.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@spicysouvlaki
spicysouvlaki marked this pull request as ready for review November 4, 2026 00:49
@spicysouvlaki
spicysouvlaki requested a review from a team as a code owner November 4, 2026 00:49
@spicysouvlaki
spicysouvlaki requested a review from jtoar November 4, 2026 00:49
sheona-harry
sheona-harry approved these changes Nov 4, 2026
View reviewed changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sheona-harry sheona-harry sheona-harry approved these changes
@jtoar jtoar Awaiting requested review from jtoar

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@spicysouvlaki @sheona-harry
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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.