### Rationale for this change
Ubuntu 26.04 will be the next LTS for Ubuntu. It'll be released on 2026-04.
### What changes are included in this PR?
* Add `Dockerfile`s for Ubuntu 26.04
* Add Ubuntu 26.04 entries
* Add a labeler configuration for Linux packages
### Are these changes tested?
Yes.
### Are there any user-facing changes?
Yes.
* GitHub Issue: #49341
Authored-by: Sutou Kouhei <kou@clear-code.com>
Signed-off-by: Raúl Cumplido <raulcumplido@gmail.com>
### Rationale for this change
#48594
### What changes are included in this PR?
- Resolve caching issue inside ODBC CI, so build time is generally less than 1hr
- Removed environment variables that are not necessary for ODBC building to keep workflow simple
- Changed ODBC workflow to be triggered when ODBC files are changed
- Add `CI: Extra: C++` label when ODBC files pr C++ Extra workflow is changed
### Are these changes tested?
- Tested in CI
### Are there any user-facing changes?
N/A
* GitHub Issue: #48594
Authored-by: Alina (Xi) Li <alina.li@improving.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
T### Rationale for this change
We've moved `csharp/` to https://github.com/apache/arrow-dotnet .
### What changes are included in this PR?
Remove `csharp/` and related files.
### Are these changes tested?
Yes.
### Are there any user-facing changes?
Yes.
* GitHub Issue: #47523
Authored-by: Sutou Kouhei <kou@clear-code.com>
Signed-off-by: Raúl Cumplido <raulcumplido@gmail.com>
### Rationale for this change
The config for Java, Go, JS and Swift on those files is not relevant anymore.
### What changes are included in this PR?
Remove references for those implementations from labeler, codeowners and editorconfig files.
### Are these changes tested?
No
### Are there any user-facing changes?
No
* GitHub Issue: #46801
Authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
### Rationale for this change
This is a follow up from: https://github.com/apache/arrow/pull/44975#issuecomment-2529683575
### What changes are included in this PR?
Fix the issue_check workflow to not assume all PRs are going to have an associated issue. Fix the worflow for minor issues.
### Are these changes tested?
I've tested on my fork.
### Are there any user-facing changes?
No
Authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
### Rationale for this change
The current implementation works for `GH-XXX` PRs but doesn't work for `MINOR` PRs.
### What changes are included in this PR?
Add a missing `issue.kind` check.
### Are these changes tested?
Yes.
### Are there any user-facing changes?
No.
* GitHub Issue: #44974
Authored-by: Antoine Pitrou <antoine@python.org>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
### Rationale for this change
It's removed by #44936.
### What changes are included in this PR?
Remove `getJiraInfo` from `exports`.
### Are these changes tested?
No. But this will resolve the reported error.
### Are there any user-facing changes?
No.
Authored-by: Sutou Kouhei <kou@clear-code.com>
Signed-off-by: Antoine Pitrou <antoine@python.org>
### Rationale for this change
We are not using JIRA anymore in the project
### What changes are included in this PR?
Remove JIRA from:
- documentation
- pr and issue templates
- comment bot
- merge script
### Are these changes tested?
Via CI
### Are there any user-facing changes?
No
* GitHub Issue: #44934
Lead-authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Co-authored-by: Jacob Wujciak-Jens <jacob@wujciak.de>
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
Signed-off-by: Jacob Wujciak-Jens <jacob@wujciak.de>
### Rationale for this change
We don't need CI in apache/arrow except integration test because we're moving the Java implementation to apache/arrow-java.
### What changes are included in this PR?
Remove Java related CI.
### Are these changes tested?
Yes.
### Are there any user-facing changes?
No.
* GitHub Issue: #44829
Authored-by: Sutou Kouhei <kou@clear-code.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Bumps [actions/labeler](https://github.com/actions/labeler) from 4.3.0 to 5.0.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/actions/labeler/releases">actions/labeler's releases</a>.</em></p>
<blockquote>
<h2>v5.0.0</h2>
<h2>What's Changed</h2>
<p>This release contains the following breaking changes:</p>
<ol>
<li>
<p>The ability to apply labels based on the names of base and/or head branches was added (<a href="https://redirect.github.com/actions/labeler/issues/186">#186</a> and <a href="https://redirect.github.com/actions/labeler/issues/54">#54</a>). The match object for changed files was expanded with new combinations in order to make it more intuitive and flexible (<a href="https://redirect.github.com/actions/labeler/issues/423">#423</a> and <a href="https://redirect.github.com/actions/labeler/issues/101">#101</a>). As a result, the configuration file structure was significantly redesigned and is not compatible with the structure of the previous version. Please read the <a href="https://github.com/actions/labeler/tree/main#pull-request-labeler">action documentation</a> to find out how to adapt your configuration files for use with the new action version.</p>
</li>
<li>
<p>The bug related to the <code>sync-labels</code> input was fixed (<a href="https://redirect.github.com/actions/labeler/issues/112">#112</a>). Now the input value is read correctly.</p>
</li>
<li>
<p>By default, <code>dot</code> input is set to <code>true</code>. Now, paths starting with a dot (e.g. <code>.github</code>) are matched by default.</p>
</li>
<li>
<p>Version 5 of this action updated the <a href="https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions">runtime to Node.js 20</a>. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20.</p>
</li>
</ol>
<p>For more information, please read the <a href="https://github.com/actions/labeler/tree/main#pull-request-labeler">action documentation</a>.</p>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/joshdales"><code>@joshdales</code></a> made their first contribution in <a href="https://redirect.github.com/actions/labeler/pull/203">actions/labeler#203</a></li>
<li><a href="https://github.com/dusan-trickovic"><code>@dusan-trickovic</code></a> made their first contribution in <a href="https://redirect.github.com/actions/labeler/pull/626">actions/labeler#626</a></li>
<li><a href="https://github.com/sungh0lim"><code>@sungh0lim</code></a> made their first contribution in <a href="https://redirect.github.com/actions/labeler/pull/630">actions/labeler#630</a></li>
<li><a href="https://github.com/TrianguloY"><code>@TrianguloY</code></a> made their first contribution in <a href="https://redirect.github.com/actions/labeler/pull/629">actions/labeler#629</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/actions/labeler/compare/v4...v5.0.0">https://github.com/actions/labeler/compare/v4...v5.0.0</a></p>
<h2>v5.0.0-beta.1</h2>
<h2>What's Changed</h2>
<p>In scope of this beta release, the structure of the configuration file (<code>.github/labeler.yml</code>) was changed from</p>
<pre lang="yml"><code>LabelName:
- any:
- changed-files: ['list', 'of', 'globs']
- base-branch: ['list', 'of', 'regexps']
- head-branch: ['list', 'of', 'regexps']
- all:
- changed-files: ['list', 'of', 'globs']
- base-branch: ['list', 'of', 'regexps']
- head-branch: ['list', 'of', 'regexps']
</code></pre>
<p>to</p>
<pre lang="yml"><code>LabelName:
- any:
- changed-files:
- AnyGlobToAnyFile: ['list', 'of', 'globs']
- AnyGlobToAllFiles: ['list', 'of', 'globs']
- AllGlobsToAnyFile: ['list', 'of', 'globs']
- AllGlobsToAllFiles: ['list', 'of', 'globs']
- base-branch: ['list', 'of', 'regexps']
- head-branch: ['list', 'of', 'regexps']
- all:
- changed-files:
- AnyGlobToAnyFile: ['list', 'of', 'globs']
- AnyGlobToAllFiles: ['list', 'of', 'globs']
- AllGlobsToAnyFile: ['list', 'of', 'globs']
</tr></table>
</code></pre>
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="8558fd7429"><code>8558fd7</code></a> Merge pull request <a href="https://redirect.github.com/actions/labeler/issues/709">#709</a> from actions/v5.0.0-beta</li>
<li><a href="000ca75fe6"><code>000ca75</code></a> Merge pull request <a href="https://redirect.github.com/actions/labeler/issues/700">#700</a> from MaksimZhukov/apply-suggestions-and-update-docume...</li>
<li><a href="cb66c2f078"><code>cb66c2f</code></a> Update dist</li>
<li><a href="9181355e36"><code>9181355</code></a> Apply suggestions for the beta vesrion and update the documentation</li>
<li><a href="efe4c1c90e"><code>efe4c1c</code></a> Merge pull request <a href="https://redirect.github.com/actions/labeler/issues/699">#699</a> from MaksimZhukov/update-node-runtime-and-dependencies</li>
<li><a href="c0957ad7c3"><code>c0957ad</code></a> Run Prettier</li>
<li><a href="8dc8d1842f"><code>8dc8d18</code></a> Update Node.js version in reusable workflows</li>
<li><a href="d0d0bbebfb"><code>d0d0bbe</code></a> Update documentation</li>
<li><a href="1375c42512"><code>1375c42</code></a> 5.0.0</li>
<li><a href="ab7411ec21"><code>ab7411e</code></a> Change version of Node.js runtime to node20</li>
<li>Additional commits viewable in <a href="ac9175f8a1...8558fd7429">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
You can trigger a rebase of this PR by commenting `@ dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@ dependabot rebase` will rebase this PR
- `@ dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@ dependabot merge` will merge this PR after your CI passes on it
- `@ dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@ dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@ dependabot reopen` will reopen this PR if it is closed
- `@ dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@ dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@ dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@ dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@ dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
> **Note**
> Automatic rebases have been disabled on this pull request as it has been open for over 30 days.
Lead-authored-by: Jacob Wujciak-Jens <jacob@wujciak.de>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Signed-off-by: Jacob Wujciak-Jens <jacob@wujciak.de>
### Rationale for this change
We have Gandiva related codes. So "C++ -" isn't match the current code base.
### What changes are included in this PR?
Remove the "C++ - " part.
### Are these changes tested?
No.
### Are there any user-facing changes?
No.
* GitHub Issue: #44223
Authored-by: Sutou Kouhei <kou@clear-code.com>
Signed-off-by: Raúl Cumplido <raulcumplido@gmail.com>
For some reason, https://github.com/apache/arrow/pull/14783 changed the automatic GH issue link to a "Closes" reference that will forcefully close the linked issue *even if the committer chooses not to close the issue using the merge script*.
Since the original change was done without discussion, this is a MINOR PR as well.
Authored-by: Antoine Pitrou <antoine@python.org>
Signed-off-by: Antoine Pitrou <antoine@python.org>
### Rationale for this change
Now, the link of CONTRIBUTING.md is broken:
```
Please read our [development documentation](https://arrow.apache.org/docs/developers/contributing.html)
```
### What changes are included in this PR?
Replace the original link by current link to docs about development.
### Are these changes tested?
Yes.
### Are there any user-facing changes?
No.
Authored-by: John <thespica@qq.com>
Signed-off-by: AlenkaF <frim.alenka@gmail.com>
### Rationale for this change
### What changes are included in this PR?
Spelling fixes to .github/
### Are these changes tested?
### Are there any user-facing changes?
* Closes: #38921
Authored-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
### Rationale for this change
We already have the "Component: Swift" label but it's not added to Swift related PRs automatically.
### What changes are included in this PR?
Add a configuration for labeler.
### Are these changes tested?
No. I want to test this on main.
### Are there any user-facing changes?
No.
* Closes: #36570
Authored-by: Sutou Kouhei <kou@clear-code.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
### Rationale for this change
Fix a bug when PR body is empty and Dev workflow fails.
### What changes are included in this PR?
Ensure the link issue comment works in case of description being empty.
### Are these changes tested?
I have tested it on my fork here: https://github.com/raulcd/arrow/pull/81
### Are there any user-facing changes?
No
* Closes: #35943
Authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Signed-off-by: Raúl Cumplido <raulcumplido@gmail.com>
The rest api calls were moved into from `github.` to `github.rest.` so the workflows are failing after the update to gh script v6.
### Are these changes tested?
As these changes are in priviliged workflows testing is only possible after merge.
Closes#36224
Authored-by: Jacob Wujciak-Jens <jacob@wujciak.de>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
### Rationale for this change
We are duplicating the Closes issue_id comment on PRs adding it to both the PR body and a comment. There was some discussion to remove it from the comment.
### What changes are included in this PR?
Remove adding extra comment to PR and check whether `Closes XXX` was already added on the body instead of checking comment.
### Are these changes tested?
Yes, I have tested on my fork, see this PR: https://github.com/raulcd/arrow/pull/79
### Are there any user-facing changes?
No
* Closes: #14790
Lead-authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
Signed-off-by: Raúl Cumplido <raulcumplido@gmail.com>
Now that all issues from JIRA are migrated to GitHub we should always use the GH corresponding issue on the PR title
* Closes: #33610
Authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Signed-off-by: Jacob Wujciak-Jens <jacob@wujciak.de>
AFAIK the `docs` label needs to be created manually for this to work.
I added the files extensions that I know are used for documentation, to add the docs label in addition to a language label and not only for changes in `docs/`.
@pitrou could you have a look?
Authored-by: Jacob Wujciak-Jens <jacob@wujciak.de>
Signed-off-by: Antoine Pitrou <antoine@python.org>
Because the Julia implementation has been moved to apache/arrow-julia.
Closes#12730 from kou/julia-remove
Authored-by: Sutou Kouhei <kou@clear-code.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
