Skip to content

Conversation

@raulcd
Copy link
Member

@raulcd raulcd commented Jan 13, 2026

Rationale for this change

With the change we did for immutable releases we required draft releases to be able to keep uploading artifacts during the release process. This means that the interim URL to download assets isn't the expected one on some of our scripts.

What changes are included in this PR?

Update the download_rc_archive task so we use the GitHub cli tool instead of manually building the download URL for the source tar.gz from the release.
Update order of release scripts to publish the release before running verification tasks so the URL is the final one.

Are these changes tested?

I have manually tested both the gh release download script and that the final URL will be the expected one once we move from draft to published release. I've tested creating a new release on my own fork here:
https://github.com/raulcd/arrow/releases/tag/test-release-rc2

Are there any user-facing changes?

No

…ckages and publish draft release before verification
@github-actions
Copy link

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

@raulcd
Copy link
Member Author

raulcd commented Jan 13, 2026

@kou if you can take a look at this, otherwise I'll merge later today (for me) and will create a new RC

Copy link
Member

@kou kou left a comment

Choose a reason for hiding this comment

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

+1

@github-actions github-actions bot added awaiting merge Awaiting merge and removed awaiting committer review Awaiting committer review labels Jan 13, 2026
@raulcd raulcd merged commit 4e5f7ea into apache:main Jan 13, 2026
15 checks passed
@raulcd raulcd removed the awaiting merge Awaiting merge label Jan 13, 2026
raulcd added a commit that referenced this pull request Jan 13, 2026
… and publish draft release before verification (#48839)

### Rationale for this change

With the change we did for immutable releases we required draft releases to be able to keep uploading artifacts during the release process. This means that the interim URL to download assets isn't the expected one on some of our scripts.

### What changes are included in this PR?

Update the `download_rc_archive` task so we use the GitHub cli tool instead of manually building the download URL for the source tar.gz from the release.
Update order of release scripts to publish the release before running verification tasks so the URL is the final one.

### Are these changes tested?

I have manually tested both the `gh release download` script and that the final URL will be the expected one once we move from draft to published release. I've tested creating a new release on my own fork here:
https://github.com/raulcd/arrow/releases/tag/test-release-rc2

### Are there any user-facing changes?

No

* GitHub Issue: #48838

Authored-by: Raúl Cumplido <[email protected]>
Signed-off-by: Raúl Cumplido <[email protected]>
raulcd added a commit that referenced this pull request Jan 13, 2026
… Packaging jobs (#48842)

### Rationale for this change

With:
- #48839

We use `gh release download`. This requires the GH_TOKEN available.

### What changes are included in this PR?

Add env with `GH_TOKEN`. I've validate the Rake's `sh` should inherit the environment variables that are defined on your shell.

### Are these changes tested?

No

### Are there any user-facing changes?
No

* GitHub Issue: #48841

Authored-by: Raúl Cumplido <[email protected]>
Signed-off-by: Raúl Cumplido <[email protected]>
raulcd added a commit that referenced this pull request Jan 13, 2026
… Packaging jobs (#48842)

### Rationale for this change

With:
- #48839

We use `gh release download`. This requires the GH_TOKEN available.

### What changes are included in this PR?

Add env with `GH_TOKEN`. I've validate the Rake's `sh` should inherit the environment variables that are defined on your shell.

### Are these changes tested?

No

### Are there any user-facing changes?
No

* GitHub Issue: #48841

Authored-by: Raúl Cumplido <[email protected]>
Signed-off-by: Raúl Cumplido <[email protected]>
@conbench-apache-arrow
Copy link

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

There weren't enough matching historic benchmark results to make a call on whether there were regressions.

The full Conbench report has more details.

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