Skip to content

CI: version PRs opened by automation never get TypeScript or Python CI #5110

Closed

Description

@cliffhall

Problem

The Version Packages PR (changesets action) and the Prepare Python Release PR are opened and updated with the workflow's GITHUB_TOKEN, which starts no workflows. RELEASING.md and the release skill say to close and reopen such a PR to start CI, but since #5048 the TypeScript and Python workflows run on push only: a reopen fires pull_request, which reaches only dco.yml. So an automated version PR never gets TypeScript or Python CI; #4941 had no check runs.

Found by Copilot on the v1.0.0 merge PR #5090. v1.0.0 was not affected (its version changes were made by hand), but the next release would be.

Expected

A version PR opened by automation is validated by the same TypeScript and Python CI as any other PR before it merges: for example, the workflows dispatch (or workflow_call) CI for the PR's head after opening or updating it, or the PR is opened with a credential whose events start workflows (the GitHub App of #5061). RELEASING.md and the release skill describe the working path, not close-and-reopen.

Activity

  1. added this to the v2.0.0 milestone on Oct 10, 2026
  2. added
    choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior change
    on Oct 10, 2026
  3. self-assigned this
    on Oct 13, 2026
  4. cliffhall commented on Oct 13, 2026

    @cliffhall
    MemberAuthor

    Shipped in #5146.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior changev2

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions