Bump galaxy-mcp pin to >=1.9.0 for the Pages tools; cut 0.5.1#346
Merged
Conversation
…olves the 1.9 release with the Pages (notebook/report) tools instead of serving the cached 1.8 build. Kept it as a >= range so future patches still resolve, and synced the two doc comments that quote the pin.
dannon
force-pushed
the
galaxy-mcp-1.9-bump
branch
from
08d1a81 to
d499ed7
Compare
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.
galaxy-mcp 1.9.0 is on PyPI now -- it's the release that adds the Pages (notebook/report) tools, fixes JSON-string
invoke_workflowinputs, and lands an auth-replay fix. Loom launches the standalone server withuvx galaxy-mcp>=1.8.0, and with that floor uvx happily keeps resolving the cached 1.8.0 and never sees the new tools. Bumping the floor to>=1.9.0forces uvx to resolve the new release and sidesteps the uv cache staleness.Kept it as a
>=range (not a pin) so future patches still resolve. The functional change is the one line inbin/loom.js; the two doc comments inbin/uvx-check.jsandapp/forge.config.tsthat quote the pin are bumped to match.Also cuts the patch release -- 0.5.1 in both package.json/lockfiles (lockstep passes) plus a CHANGELOG highlight, same as the 0.4.1 entry did for the 1.6 -> 1.8 bump.
Verified: root + app typecheck clean, 1222 tests pass, prettier clean on touched files.
Note for after release: uvx may need a
uv cacherefresh to pick up the new resolve on machines that already cached 1.8.0.