Skip to content

AutoMerge: Migrate from juliaup_jll to directly using versions.json - #706

Draft
DilumAluthge wants to merge 1 commit into
masterfrom
dpa/versions-json
Draft

DilumAluthge wants to merge 1 commit into
masterfrom
dpa/versions-json

Conversation

@DilumAluthge

@DilumAluthge DilumAluthge commented Mar 31, 2026

Copy link
Copy Markdown
Member

This PR migrates from juliaup_jll and instead directly depends upon versions.json.

versions.json is the upstream source for tools such as Juliaup and julia-actions/setup-julia. We try to avoid making breaking changes in versions.json, so I think it will be more stable to directly depend on versions.json (instead of depending on Juliaup).

The PR adds a submodule named AutoMerge.DownloadJuliaVersions. For now, the code can live inside of AutoMerge, but we could eventually consider pulling it out into its own package so that other people can use it without needing to pull in all of AutoMerge.

The code is relatively straightforward:

  1. Download versions.json from S3, and parse it.
  2. Make a list of all Julia versions that have native binaries for the host platform.
  3. When a Julia version is provided, download and extract the Julia tarball as an artifact (for persistence across sessions).

@DilumAluthge
DilumAluthge force-pushed the dpa/versions-json branch 2 times, most recently from da8e3a2 to 9f8bdb1 Compare April 6, 2026 19:42
@DilumAluthge DilumAluthge changed the title WIP: AutoMerge: Migrate from juliaup_jll to directly using versions.json AutoMerge: Migrate from juliaup_jll to directly using versions.json Apr 7, 2026
@JuliaRegistries JuliaRegistries deleted a comment from codecov Bot Sep 5, 2026

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant