Skip to content

ci: probe release PR and tag paths (do not merge) - #406

Closed
deanq wants to merge 2 commits into
mainfrom
deanq/release-flow-probe
Closed

deanq wants to merge 2 commits into
mainfrom
deanq/release-flow-probe

Conversation

@deanq

@deanq deanq commented Oct 30, 2026

Copy link
Copy Markdown
Member

Temporary probe for #405. It checks two things:

  • GITHUB_TOKEN can tag main HEAD.
  • A PR opened with the release app token on a release-please-- branch starts CI and passes Validation.

The probe PR it opens closes itself, and the probe tag is deleted. This PR gets closed without merging.

🤖 Generated with Claude Code

deanq added 2 commits October 30, 2026 15:08
Since #401 the built-in token handles both tagging and release PRs.
GitHub does not start pull_request workflows for events made with the
built-in token, so the next release PR would never get the required
Validation check, and ci.yml's Guard expects runpod-release-please-bot
as the author.

Run release-please twice: the built-in token tags and creates releases
(skip-github-pull-request), then the app token opens or updates the
release PR (skip-github-release). The app does not need the workflows
permission for PRs.
@deanq

deanq commented Oct 30, 2026

Copy link
Copy Markdown
Member Author

Probe done: tag 201 on main HEAD; app-opened release-please-- PR #407 got Guard bypass and Validation success. Closing without merge.

@deanq deanq closed this Oct 30, 2026
@deanq
deanq deleted the deanq/release-flow-probe branch October 30, 2026 22:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant