Skip to content

GH-50336: [Release][Archery] Fix archery GitHub integration for release scripts#50337

Merged
kou merged 2 commits into
apache:mainfrom
raulcd:GH-50336
Jul 2, 2026
Merged

GH-50336: [Release][Archery] Fix archery GitHub integration for release scripts#50337
kou merged 2 commits into
apache:mainfrom
raulcd:GH-50336

Conversation

@raulcd

@raulcd raulcd commented Jul 2, 2026

Copy link
Copy Markdown
Member

Rationale for this change

The source verification and binary verification scripts comment to the Verification PR were failing due to the last updates to archery in order to use a single dependency.

What changes are included in this PR?

Add required base and head branches to be used when looking for a PR.

Use create_issue_comment on PRs instead of create_comment which tries to create a review comment which requires more arguments.

Are these changes tested?

Yes, I've tested them locally in isolation in order to add comments on the verification PR.

Are there any user-facing changes?

No

Copilot AI review requested due to automatic review settings July 2, 2026 13:45
@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown

⚠️ GitHub issue #50336 has been automatically assigned in GitHub to PR creator.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes Archery’s GitHub PR interaction for release automation by ensuring PR lookup includes the necessary base/head branches and by posting standard PR issue comments (not review comments) from release/verification flows.

Changes:

  • Add --base-branch / --head-branch options to archery crossbow report-pr and pass them into Repo.github_pr(...) PR lookup.
  • Switch PR commenting to create_issue_comment(...) (both for verify-release-candidate triggers and for report-pr job tracking comments).
  • Update dev/release/03-binary-submit.sh to pass base/head branches when calling archery crossbow report-pr.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
dev/release/03-binary-submit.sh Pass base/head branch args to archery crossbow report-pr for release PR tracking.
dev/archery/archery/crossbow/cli.py Add base/head options to report_pr and use create_issue_comment for PR comments.

Comment thread dev/release/03-binary-submit.sh Outdated

@kou kou left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@kou kou merged commit d433ffc into apache:main Jul 2, 2026
31 checks passed
@kou kou removed the awaiting committer review Awaiting committer review label Jul 2, 2026
@github-actions github-actions Bot added the awaiting merge Awaiting merge label Jul 2, 2026
@raulcd raulcd deleted the GH-50336 branch July 3, 2026 07:37
raulcd added a commit that referenced this pull request Jul 3, 2026
…se scripts (#50337)

### Rationale for this change

The source verification and binary verification scripts comment to the Verification PR were failing due to the last updates to archery in order to use a single dependency.

### What changes are included in this PR?

Add required base and head branches to be used when looking for a PR.

Use create_issue_comment on PRs instead of create_comment which tries to create a review comment which requires more arguments.

### Are these changes tested?

Yes, I've tested them locally in isolation in order to add comments on the verification PR.

### Are there any user-facing changes?

No

* GitHub Issue: #50336

Authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
@conbench-apache-arrow

Copy link
Copy Markdown

After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit d433ffc.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 5 possible false positives for unstable benchmarks that are known to sometimes produce them.

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

Labels

awaiting merge Awaiting merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants