Add an only-version input for targeted single-version updates - #103
Merged
Conversation
Give the workflow one version (e.g. 1.13.0-rc3) and it downloads exactly that version's files and updates versions.json with exactly that version; every other seeded entry is carried over untouched. Refuses a version that isn't a julia tag, and refuses to run without a seeded versions.json (the result would contain only that version). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Member
Author
|
I have a backup and will just test this to see how it works in practice. It worked well locally. |
Member
Author
|
This worked ok https://github.com/JuliaLang/VersionsJSONUtil.jl/actions/runs/31785004778/job/94718864946. Took 4 minutes. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an
only-versiontext input to the Run workflow dialog. Give it one version (e.g.1.13.0-rc3) and the build downloads exactly that version's files and updatesversions.jsonwith exactly that version — every other seeded entry is carried over untouched, with no HEAD sweep over the rest of the grid. This makes the release-day update a targeted, fast run instead of a full pass over every tag.Safety guards:
versions.jsonis present, since the result would contain only that one versionLeft empty (or on push-triggered runs) the behavior is unchanged from
main.Tested locally against the currently deployed
versions.jsonwithonly_version = "1.13.0-rc3": it downloaded rc3's 14 files, the resulting file's only added key is1.13.0-rc3(byte-identical to what a full incremental run produces), and it passes the schema check andtest/more_tests.jl.🤖 Generated with Claude Code