feat(cli): add mops toolchain info --versions#609
Merged
Conversation
Scripts can now list all stable GitHub release tags for toolchain tools, matching `mops info --versions` for packages. Also paginates release fetches so version pickers and latest resolution see the full history. Co-authored-by: Cursor <cursoragent@cursor.com>
Use getLatestReleaseTag for displayed latest, restore bounded getReleases for the interactive picker, and fast-path latest resolution pagination. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Cursor AI review👍 APPROVE — looks safe to merge
VerdictDecision: APPROVE Generated for commit 607e711 |
Avoid full GitHub pagination for the human summary and --versions; add --all for full history. Note flipping mops info --versions in NEXT-MAJOR. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.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
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.
Scripts can list stable GitHub releases for toolchain tools (moc, lintoko, wasmtime, pocket-ic) — the missing counterpart to
mops info <package> --versions.Before:
After:
$ mops toolchain info lintoko lintoko latest: 0.11.0 pinned 0.7.0 repository https://github.com/caffeinelabs/lintoko versions 0.11.0, 0.10.0, 0.9.0, 0.8.0, 0.7.0, 0.6.0, 0.5.1, 0.5.0, 0.4.3, 0.4.2 (+7 more) $ mops toolchain info moc --versions | head -5 1.11.0 1.10.1 1.10.0 1.9.0 1.8.2--versionsprints newest first and fetches only the first GitHub releases page by default. Pass--versions --allfor the full history (cache warming). Humaninfoalso uses the first page only — it does not paginate the whole release list just to show ~10 versions.--versionsexcludes drafts and prereleases. Stable versions match whatmops toolchain updateandmops toolchain use <tool> latestresolve to. Interactivemops toolchain usewithout a version may still show prereleases in its picker.Works without a
mops.toml.What is unchanged
mops toolchain use,update, andbinbehavior is unchanged aside from paginated latest resolution (stops at the first stable release instead of scanning only the first 10).mops info <pkg> --versionsstill prints oldest→newest. Flipping that to newest-first (to match this command) is tracked inNEXT-MAJOR.md.