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

safe-global / safe-client-gateway / 37766705002
90%

Build:
DEFAULT BRANCH: main
Ran 08 Oct 2026 11:08AM UTC
Jobs 2
Files 1044
Run time 3min
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

08 Oct 2026 10:55AM UTC coverage: 89.863% (+0.3%) from 89.555%
37766705002

push

github

web-flow
fix: close Safe Queue Service rollout gaps (#3553)

* fix: close Safe Queue Service rollout gaps

- serve pending data from the queue service and executed data from the transaction service: propose pre-check, tx-details rejectors, and an executed-only multisig-transactions list (executed param deprecated)
- deprecate delegates v1/v2 in favour of v3 and move the push-notification delegate check to the v3 repository
- accept a null delegate chainId and forward the label filter
- cap queue list limits at the queue service maximum
- await delegate cache invalidation
- add flag-on integration coverage for transactions, safes, delegates v3 and hooks cache invalidation

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: address review feedback on queue rollout gaps

- always request executed transactions from the transaction service on the multisig-transactions list when the flag is on, and drop the executed param deprecation
- read rejectors of a consumed nonce from the transaction service without the executed-only filter
- cap queue limits only on the outgoing request
- drop the toJson helpers from the queue test builders

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(safe): read rejectors only from the queue service when the flag is on

Rejectors only matter for pending transactions, and no client reads them for executed ones. With the flag on, a pending nonce is read from the queue service and a consumed nonce returns no rejectors without any upstream call. The flag-off path is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(transactions): stop resolving rejectors and deprecate the field

No client reads `detailedExecutionInfo.rejectors`: across the wallet monorepo (web and mobile, on dev and main) it appears only in the generated API types and test fixtures. Resolving it cost an upstream list call per transaction-details request, and with the queue service enabled it meant fetching the whole queue... (continued)

4634 of 5399 branches covered (85.83%)

Branch coverage included in aggregate %.

20 of 20 new or added lines in 6 files covered. (100.0%)

11713 of 12792 relevant lines covered (91.57%)

524.49 hits per line

Jobs
ID Job ID Ran Files Coverage
1 run-integration-tests - 37766705002.1 08 Oct 2026 11:09AM UTC 1044
66.21
GitHub Action Run
2 run-unit-tests - 37766705002.2 08 Oct 2026 11:08AM UTC 1044
67.27
GitHub Action Run
Source Files on build 37766705002
  • Tree
  • List 1044
  • Changed 29
  • Source Changed 12
  • Coverage Changed 22
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #37766705002
  • 34a18a5a on github
  • Prev Build on main (#37766663204)
  • Next Build on main (#37805275981)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc