• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

safe-global / safe-client-gateway / 20059132802 / 1
90%
main: 89%

Build:
Build:
LAST BUILD BRANCH: feat/v3-owners-enpoint-and-pagination
DEFAULT BRANCH: main
Ran 09 Dec 2025 09:56AM UTC
Files 1883
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

09 Dec 2025 09:49AM UTC coverage: 53.579%. Remained the same
20059132802.1

Pull #2839

github

katspaugh
refactor(cache): change Zerion cache keys to be per address only

Remove chainId from Zerion cache keys for balances, collectibles, and positions.
This changes the caching strategy from per-chain-per-address to per-address only,
allowing data to be shared across chains for the same address.

Cache key changes:
- Before: {chainId}_zerion_balances_{safeAddress}
- After: zerion_balances_{safeAddress}

Similar changes applied to positions and collectibles cache keys.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Prettier
Pull Request #2839: refactor(cache): change Zerion cache keys to be per address only

737 of 3741 branches covered (19.7%)

Branch coverage included in aggregate %.

16837 of 29059 relevant lines covered (57.94%)

3.65 hits per line

Source Files on job run-integration-tests - 20059132802.1
  • Tree
  • List 1883
  • Changed 269
  • Source Changed 3
  • Coverage Changed 269
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 20059132802
  • 850f9bb9 on github
  • Prev Job for on refactor/zerion-cache-per-address (#20054993733.2)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc