Add automated release sync for _data/releases.yaml#2818
Open
holly-cummins wants to merge 1 commit into
Open
Conversation
This comment has been minimized.
This comment has been minimized.
|
🎊 PR Preview ecc1427 has been successfully built and deployed to https://quarkus-website-pr-2818-preview.surge.sh
|
holly-cummins
force-pushed
the
auto-update-releases-yaml
branch
from
a6f827f to
289c003
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Syncs patch versions from GitHub API on a schedule. Manual fields (policy, support_providers, eol_support, lts, eol_date, links) are preserved - only latest_patch and latest_patch_date are automated. - tools/releases-sync/main.java: JBang script fetching from GitHub API - .github/workflows/sync-releases.yml: scheduled sync + PR dry-run Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> Co-Authored-By: Claude Sonnet 4 <noreply@anthropic.com>
holly-cummins
force-pushed
the
auto-update-releases-yaml
branch
from
2fe5374 to
90f26b5
Compare
Contributor
Author
|
This is now good to go. The sync releases workflow does a dry run on PRs, and I think the diff is looking good. My automated generation did some corrections over the previous vibe-coded list, such as amending some release dates, and adding .Final suffixes where needed. it also added releases further back, through 1 and 0 versions. The latest build has this as the start of the diff: |
Status for workflow
|
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
2 participants
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.
When I did #2750, I said I'd do a follow-on so that the data generation wasn't manual. This is that follow-on.
The file is a slightly awkward mix of stuff we'd want to maintain manually, and stuff we'd want to automate. The updater is coded to recognise that, and only change things it's supposed to change.
It will try and predict the next version after a release makes the current next-version obsolete, but if we update it manually, that value will stick.
Manual fields (policy, support_providers, eol_support, lts, eol_date, links) are preserved - only latest_patch and latest_patch_date are automated. We may want to extend to also automate some of that information, but I thought I'd start modestly.