chore(deps): bump @alphafi/stsui-sdk to 2.0.3 - #93
Merged
Conversation
Picks up the GraphQL TypeName event-filter fix (stsui-sdk#42). The lockfile was pinning 2.0.2, so the existing caret range never resolved to it — event reads (APR/APY, mint events) returned zeros through this SDK. Build clean against 2.0.3.
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.
Picks up stsui-sdk#42 — GraphQL renders Move's
TypeNameas a plain string, but the event filter still read.typename.name, so every event was dropped:fetchStSuiAPR/fetchStSuiAPYreturned 0 andgetMintEventsfound nothing.This repo's range was already
^2.0.2, butpackage-lock.jsonpinned the resolved version to 2.0.2, sonpm cinever picked the fix up. Both are updated here.Lockfile delta is limited to
@alphafi/stsui-sdk2.0.2 → 2.0.3 plus the removal of the nestedtypedoc/shikisubtree that 2.0.2 pulled in — no other package versions move.Verified:
npm ciinstalls 2.0.3 andnpm run buildis clean, which also confirms thetypenametype narrowing ({ name: string }→string) breaks nothing here.After merge, this package needs a republish so its own consumers (
alphafi-mcp,integration-api/lambdas/alpha-unlocks) inherit the fix.