Skip to content

fix(ci): build changelog in regeneration PR, not via protected-branch push (httpx) - #404

Merged
TKIPisalegacycipher merged 1 commit into
httpxfrom
ci/changelog-in-regen-httpx
Jun 10, 2026
Merged

fix(ci): build changelog in regeneration PR, not via protected-branch push (httpx)#404
TKIPisalegacycipher merged 1 commit into
httpxfrom
ci/changelog-in-regen-httpx

Conversation

@TKIPisalegacycipher

Copy link
Copy Markdown
Collaborator

Cherry-pick of #402 (0904f77) per the infra-distribution rule (cherry-pick across branches, never merge main down).

Removes the protected-branch changelog push from create-release.yml and builds the changelog inside the regeneration PR (regenerate-library.yml) so it rides the required checks. Drift auto-merged cleanly.

… push (#402)

create-release.yml's "Build changelog" step rendered CHANGELOG.md and pushed
the commit straight to the release branch (main/beta/httpx). Those branches
require status checks, and a bot commit pushed directly has none, so the push
was rejected with GH013 (run 27302232244):

    remote: error: GH013: Repository rule violations found for refs/heads/httpx
    - 9 of 9 required status checks are expected.

The step also ran unconditionally, so it fired even when the release already
existed and "Create release" was skipped. The changelog edit never fails the
checks; it just never reached them.

Move the towncrier build into regenerate-library.yml, right after the version
bump, so the rendered CHANGELOG.md and consumed fragments ride the regeneration
PR through its required checks (towncrier is in the dev group, already synced).
Drop the push step from create-release.yml; the changelog is on the branch
before the release is cut.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@TKIPisalegacycipher
TKIPisalegacycipher merged commit 34c491d into httpx Jun 10, 2026
1 check passed
@TKIPisalegacycipher
TKIPisalegacycipher deleted the ci/changelog-in-regen-httpx branch June 10, 2026 20:23
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