Skip to content

v0.1.4: Trade data correctness fixes

Choose a tag to compare

View all tags
@cyanheads cyanheads released this 10 Jun 18:21
· 8 commits to main since this release
v0.1.4
This tag was signed with the committer’s verified signature.
cyanheads Casey Hand
SSH Key Fingerprint: lkZCAfVCK5qsrcvEYCs0BnVRDCX7pKsdCZkw5yYKMuw
Verified
Learn about vigilant mode.
499c040
This commit was signed with the committer’s verified signature.
cyanheads Casey Hand
SSH Key Fingerprint: lkZCAfVCK5qsrcvEYCs0BnVRDCX7pKsdCZkw5yYKMuw
Verified
Learn about vigilant mode.

Trade data correctness fixes

Fixes three data-accuracy bugs in fetchTradeData: trade totals no longer sum dimension-expanded breakdown rows, partner rankings deduplicate per-partner, and services descriptions resolve via EBOPS instead of HS.

Fixed:

  • Trade totals now read the API's aggregate row (motCode=0/customsCode=C00/partner2Code=0); Germany 2022 exports: was ~$13.57T (sum of 90 rows), now $1.696T (#4)
  • Partner deduplication keeps max-value row per partnerCode; Poland no longer appears at two ranks (#5)
  • Services descriptions resolve via EBOPS: cmdCode=3 → Transport, not Cereals (#6)
  • RawTradeRow declares motCode, customsCode, partner2Code, isAggregate fields explicitly

Also adds CITATION.cff, manifest.json/server.json metadata alignment (COMTRADE_SUBSCRIPTION_KEY in stdio environmentVariables), and service tests.

Dependency bumps:

  • @biomejs/biome ^2.4.15 → ^2.4.16
  • @types/node ^25.9.1 → ^25.9.2
  • vitest ^4.1.7 → ^4.1.8

86 tests pass; bun run devcheck clean.

Assets 3
Loading