fix: monitor 4.0 for autobumps#18
Closed
chadlwilson wants to merge 1 commit into
Closed
Conversation
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
chadlwilson
commented
Mar 18, 2026
|
LGTM 🚀 |
Owner
|
oops I wasn't watching this repo so missed this and created #19 before I saw it |
3 tasks
Author
|
Well, the bigger problem is still that the auto-commit of new formula is broken anyway I suppose |
jdx
added a commit
that referenced
this pull request
Mar 25, 2026
## Summary - Autobump workflow now dynamically discovers minor series from ruby/ruby releases instead of a hardcoded `3.2 3.3 3.4` list - New minor versions (4.1, 5.0, etc.) will be picked up automatically without workflow changes - Fixed tag matching to handle both old underscore format (`v3_4_2`) and new dot format (`v4.0.2`) - Abstract class selection falls back to base `JdxRuby` when no version-specific class exists - Adds Ruby 4.0.2 formula Supersedes #18 — thanks @chadlwilson for identifying the issue! Co-authored-by: Chad Wilson <29788154+chadlwilson@users.noreply.github.com> ## Test plan - [ ] Trigger autobump workflow manually via `workflow_dispatch` and verify it discovers 3.2, 3.3, 3.4, 4.0 series - [ ] Verify it skips versions that already have formulae - [ ] Verify prerelease detection correctly handles dot-format tags 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > Moderate risk because it changes the automation that generates and commits new Homebrew formulae; bugs in tag parsing/series discovery could create incorrect or missing formula updates. > > **Overview** > Updates the `autobump.yml` workflow to **auto-discover supported Ruby minor series** from `ruby/ruby` releases (instead of a hardcoded list) and to **match both underscore and dot tag formats** when selecting the latest stable release. > > The workflow now **falls back to the base `Abstract/jdx-ruby` class** when a version-specific abstract (`Abstract/jdx-ruby-XX.rb`) is missing, and prerelease detection similarly recognizes stable dot-format tags. Adds a new formula for `jdx-ruby@4.0.2`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 07cec48. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
3 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.
4.0 is seemingly not being monitored right now, so 4.0.2 does not seem to have been detected.
https://github.com/jdx/ruby/actions/runs/23244154533/job/67567990377
Additionally as mentioned at #16 the autobump workflows seem to have been broken for a week (master push restriction needs to be lifted for the automation?) and thus new patch releases aren't being built/published so some intervention is needed on the GH repo.