fix: for betas, get the most recent version number from main#416
Merged
fix: for betas, get the most recent version number from main#416
Conversation
tjvantoll
changed the title
rdlauer
approved these changes
Feb 19, 2026
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.
We hit an issue where beta versions are posting with old numbers (see screenshot below).
This PR switches the CI workflow so that it pulls the latest version from the
mainbranch’sconfig.jsoninstead of relying on the branch’sconfig.jsonwhich might be stale. Claude heavily assisted me on this but it seems like a pretty safe update. Worst case we start publishing betas with bad versions and we have to fix that :)