Ruby binaries built on GitHub Actions runners are moving from a single release to one release per engine-version

[eregon]

Breaking changes

See ruby/setup-ruby#98 for context and why I'm opening an issue here.
The change is this: ruby/setup-ruby#810

Concretely, instead of being at
https://github.com/ruby/ruby-builder/releases/download/toolcache/ruby-3.4.6-ubuntu-24.04.tar.gz
(part of https://github.com/ruby/ruby-builder/releases/tag/toolcache)
it's now at
https://github.com/ruby/ruby-builder/releases/download/ruby-3.4.6/ruby-3.4.6-ubuntu-24.04-x64.tar.gz
(part of https://github.com/ruby/ruby-builder/releases/tag/ruby-3.4.6)

Note the platform naming also changed so that it always include the architecture and never -latest.

Target date

It's all done now, the old https://github.com/ruby/ruby-builder/releases/download/toolcache release will remain available for some time.

The motivation for the changes

We reached the limit of 1000 assets per release with the old approach, so now we do something similar to https://github.com/actions/python-versions

Possible impact

From a quick search I can find https://github.com/search?q=repo%3Aactions%2Frunner-images%20ruby-builder&type=code
Those should be updated, I can make a PR.

Platforms affected

• Azure DevOps
• GitHub Actions

Runner images affected

• Ubuntu 22.04
• Ubuntu 24.04
• macOS 13
• macOS 13 Arm64
• macOS 14
• macOS 14 Arm64
• macOS 15
• macOS 15 Arm64
• macOS 26 Arm64
• Windows Server 2019
• Windows Server 2022
• Windows Server 2025

Mitigation ways

n/a

[erik-bershel]

Hey @eregon!

Thanks for the announcement and the PR - I just stumbled across the crashed nightly builds . 😆

While reaching the limits is disappointing in general, I also think it's an achievement that reflects your project's growth and demonstrates how quickly you can adapt to new challenges and even help your loyal users adapt. 🙇

[erik-bershel]

I'll keep it on our board to increase users awareness for a week.

[eregon]

I just stumbled across the crashed nightly builds . 😆

Interesting, was something relying on the latest release being the toolcache one or so?

[erik-bershel]

Interesting, was something relying on the latest release being the toolcache one or so?

Our code relied on how releases were stored previously.

[eregon]

Ah yes, things like package_tar_names=$(curl -fsSL "https://api.github.com/repos/ruby/ruby-builder/releases/latest" | jq -r '.assets[].name') (from https://github.com/actions/runner-images/pull/13058/files) I see.

I could mark the toolcache release as "latest" if necessary, although when the next Ruby release comes up it would be natural if that becomes the one marked as "latest".
In any case it seems all is working now :)
Thank you for your work on these PRs.