Skip to content

Bump duneapi-client-go to v0.7.1 - #72

Merged
ivpusic merged 1 commit into
mainfrom
ivan/bump-duneapi-client-go-v0.7.1
Nov 20, 2026
Merged

ivpusic merged 1 commit into
mainfrom
ivan/bump-duneapi-client-go-v0.7.1

Conversation

@ivpusic

@ivpusic ivpusic commented Nov 20, 2026

Copy link
Copy Markdown
Member

What & why

Bumps duneapi-client-go from v0.7.0 to v0.7.1, which has one change: getResults returns the error when a results response can't be decoded (duneapi-client-go#33). Before, the error was ignored, so if a later page of a paginated result failed to decode, execution results and query run could print the earlier pages' rows as if they were the whole result.

  • go.mod/go.sum: the SDK bump; go mod tidy changes nothing else.
  • flake.nix: new vendorHash, computed as the NAR hash of go mod vendor (nix hash path), the method that reproduces main's current hash.

Tests

  • go vet ./... and go test -race ./... pass.
  • A local nix build couldn't run in the agent sandbox; the nix CI jobs build the flake and check the hash.

Blast radius: CLI users see an error instead of partial rows when the API returns an unreadable results page. Follows with a v0.1.23 release.

v0.7.1 returns the decode error from getResults (duneapi-client-go#33): an
unreadable results page now fails instead of being ignored, so a paginated
result can no longer look complete with only its earlier pages.

Amp-Thread-ID: https://ampcode.com/threads/T-01a1f35e-4422-71d4-a903-056e89e15547
Co-authored-by: Amp <amp@ampcode.com>
@ivpusic
ivpusic merged commit e5d972e into main Nov 20, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants