chore(release): v0.4.0 - #49
Merged
Merged
Conversation
Pyth-priced iAssets in the transaction builders (#47) and the retired /api/v1 indexer base (#48). npm has served 0.3.0 since 10 June, which predates the read tools moving onto /api/v3, so every npx install has been running pre-v3 read paths regardless of configuration. Merge after #47 and #48; tag v0.4.0 to trigger the publish 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
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.
Version bump only. Merge last, after #47 and #48, then tag
v0.4.0— the publish workflow fires onrefs/tags/v*.Why this matters more than a normal bump
npm has served 0.3.0 since 10 June. The commits that moved the read tools onto
/api/v3(bc17c42,b6704cd) landed the same day, just after the publish. So for two months everynpx @indigoprotocol/indigo-mcpinstall has been calling pre-v3 analytics paths —/analytics/tvl,/analytics/ada— which 404 regardless of howINDEXER_URLis configured. Verified by pointing the published package at a local echo server and reading the paths it requests.That means the current npm release is broken for read tools independently of #48, and #48's fix does not reach anyone until something is published.
What 0.4.0 carries
HOST/MCP_PORT,engines.node >= 20, iADA, and the server reporting its real version/api/v1indexer base removed from the wizard,.env.exampleandfly.toml, plus tolerance for a versionedINDEXER_URLso configs already in the wild recoverMinor rather than patch:
engines.nodemoves to>= 20, which drops Node 18 support (the server already crashed there, but the constraint is now explicit).SERVER_VERSIONis no longer hardcoded — #47 reads it from package.json — so this one-line change is the whole bump.After merging
Then re-test the original integration report against the published build: some of what was reported may have been the stale package rather than genuine gaps.