chore: bump @ecency/sdk to 2.3.68 - #3375
Conversation
Picks up the post-tips read moving from POST to GET. A POST response is uncacheable, so tips were re-requested on every mount; the GET is addressable by URL and the endpoint now serves a Cache-Control, so repeat reads come from the cache instead of the network. Mobile consumes both changed queries through the SDK (tipsQueries and proQueries), so no app-side change is needed. The server route is already live and the old POST route stays in place, so this is safe to ship whenever.
Greptile SummaryUpdates
Confidence Score: 5/5The PR appears safe to merge with no actionable issues identified in the dependency update. The manifest and lockfile consistently resolve
|
| Filename | Overview |
|---|---|
| package.json | Bumps the declared @ecency/sdk dependency from 2.3.67 to 2.3.68. |
| yarn.lock | Locks @ecency/sdk to 2.3.68 with matching resolution and integrity metadata while preserving its dependency set. |
Reviews (1): Last reviewed commit: "chore: bump @ecency/sdk to 2.3.68" | Re-trigger Greptile
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pull request updates the ChangesSDK dependency update
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Bumps
@ecency/sdk2.3.67 to 2.3.68.That release contains exactly two changes, both to queries this app already uses:
post-tipsis now read with aGETon/private-api/post-tips/{author}/{permlink}instead of aPOSTwith a JSON body. A POST response is uncacheable by definition, so the same tip totals were re-requested on every mount; the query also had nostaleTime, meaning it was stale on every mount and window refocus. Both are fixed upstream.pro-membersfreshness documented and left at 5 minutes, deliberately below the endpoint's own cache window (react-query cannot see how old a cached response already was, so matching the two would add the windows together rather than align them).No app-side change is needed:
tipsQueries.tsandproQueries.tsconsumegetPostTipsQueryOptionsandgetProMembersQueryOptionsstraight from the SDK.The server side is already deployed and the previous
POSTroute is still served, so an older build keeps working and this can ship on the normal release cadence.Verified the installed build resolves to 2.3.68 and calls the GET path with both segments encoded.
Summary by CodeRabbit