Skip to content

[v3-4-test] Hold back only build-info changes in fork CI and stop drafting them (#76282) - #76394

Merged
shahar1 merged 1 commit into
apache:v3-4-testfrom
shahar1:backport-76282-v3-4-test
Nov 6, 2026
Merged

shahar1 merged 1 commit into
apache:v3-4-testfrom
shahar1:backport-76282-v3-4-test

Conversation

@shahar1

@shahar1 shahar1 commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Backport of #76282 to v3-4-test. The automatic backport failed because #76282 builds on #76289 (add_approval_label and the note on ApprovalDecision), which is not on this branch.

#76289 is being backported separately from branch backport-76289-v3-4-test on the fork. Until that backport merges, this PR still contains both commits, in merge order:

Once the #76289 backport merges, this branch will be rebased onto v3-4-test so that only the #76282 commit remains.

Both apply cleanly in that order; the touched breeze sources and tests match main apart from #76327 (backported separately in #76368) and #76136.

Checks run: the four breeze test files touched by the two commits (545 passed) and prek run --from-ref v3-4-test --stage pre-commit.

related: #76282, #76289


Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Claude Fable 5.1)

Generated-by: Claude Code (Claude Fable 5.1) following the guidelines

🤖 Generated with Claude Code

https://claude.ai/code/session_01BVx6g9764zdPbChsFVGcKV

@shahar1

shahar1 commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor Author

Unbundling, merge #76582 before this one

…pache#76282)

A docs-only change under dev/breeze/ drafted the pull request and waited for a maintainer as if it changed CI, although only the files that decide which jobs run and on which runners (workflows, breeze sources, the breeze installation, and scripts/ci/prek/ whose provider dependencies script selective checks runs) can let a pull request steer its own CI. Such pull requests still wait for a maintainer to run project CI, but are no longer drafted, so they stay visible for review. Changes to the other files CI uses are no longer held, but are still pointed out to the reviewer in a one-time comment. The provider dependencies script now ignores uv configuration from the checkout, so a pull request cannot redirect where its dependencies come from.

Generated-by: Claude Opus 5
(cherry picked from commit 3edd052)
@shahar1
shahar1 force-pushed the backport-76282-v3-4-test branch from 14443a7 to 1daf9ed Compare November 6, 2026 09:07
@shahar1
shahar1 enabled auto-merge (squash) November 6, 2026 09:08
@shahar1
shahar1 disabled auto-merge November 6, 2026 09:08
@shahar1
shahar1 enabled auto-merge (squash) November 6, 2026 09:09
@shahar1
shahar1 merged commit dac5d28 into apache:v3-4-test Nov 6, 2026
117 checks passed
vatsrahul1001 pushed a commit that referenced this pull request Nov 9, 2026
…fting them (#76282) (#76394)

A docs-only change under dev/breeze/ drafted the pull request and waited for a maintainer as if it changed CI, although only the files that decide which jobs run and on which runners (workflows, breeze sources, the breeze installation, and scripts/ci/prek/ whose provider dependencies script selective checks runs) can let a pull request steer its own CI. Such pull requests still wait for a maintainer to run project CI, but are no longer drafted, so they stay visible for review. Changes to the other files CI uses are no longer held, but are still pointed out to the reviewer in a one-time comment. The provider dependencies script now ignores uv configuration from the checkout, so a pull request cannot redirect where its dependencies come from.

Generated-by: Claude Opus 5
(cherry picked from commit 3edd052)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants