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

safe-global / safe-client-gateway / 36111420941
89%

Build:
DEFAULT BRANCH: main
Ran 25 Sep 2026 08:13AM UTC
Jobs 2
Files 1015
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

25 Sep 2026 08:09AM UTC coverage: 89.231% (-0.02%) from 89.249%
36111420941

push

github

web-flow
ci: drop the legacy autodeploy nudge from the staging pipeline (#3488)

* ci: drop the legacy autodeploy nudge from the staging pipeline

The `notify-legacy-deploy` job posted a Docker-Hub-webhook-shaped payload to nudge the legacy controller into pulling the new `:staging` image. That controller no longer manages CGW: the devstaging Application and argocd-image-updater were retired at the 2026-09-25 cutover, and staging now renders from safe-client-gateway-infra-tf.

It was also never working. `scripts/autodeploy.sh` captured the HTTP status into `--write-out` and threw it away, and with `curl -s` and no `-f` curl exits 0 for any response, so `set -e` never saw a failure. The status check added when PR #3474 was reviewed made it visible on the first run: **HTTP 404**. The webhook had been rejecting every nudge, silently, for however long — which means argocd-image-updater's polling had been doing all the work on its own.

So the job is now a no-op that paints a red cross on every Staging run. Removed, along with the script. `AUTODEPLOY_URL` and `AUTODEPLOY_TOKEN` have no remaining reader and can be revoked (WA-3432).

The header comment is rewritten: it still described staging as deployed by the legacy path and the new Application as unapplied, both of which stopped being true at the cutover.

Two transitional pieces stay, each with its ticket named in the YAML:

  * `moving_tag: staging` (WA-3428). Nothing in the cluster consumes it now, but _build-image.yml publishes a moving tag to both registries and the Docker Hub one is public, so dropping it would also stop publishing safeglobal/safe-client-gateway-nest:staging. It waits on the external-consumer inventory.
  * `version_check_url: ""` (WA-3629). The poll runs after the deploy PR is merged, and that merge currently fails, so switching it on would change nothing. It waits until deploys merge and the timeout can be sized against a real rollout.

Verification: yarn format, yarn lint and yarn test c... (continued)

4365 of 5135 branches covered (85.0%)

Branch coverage included in aggregate %.

11122 of 12221 relevant lines covered (91.01%)

514.6 hits per line

Coverage Regressions

Lines Coverage ∆ File
1
86.67
-5.0% src/modules/notifications/routes/v1/notifications.controller.ts
1
94.35
-1.61% src/modules/transactions/routes/mappers/common/transaction-data.mapper.ts
Jobs
ID Job ID Ran Files Coverage
1 run-integration-tests - 36111420941.1 25 Sep 2026 08:15AM UTC 1015
64.11
GitHub Action Run
2 run-unit-tests - 36111420941.2 25 Sep 2026 08:13AM UTC 1015
66.12
GitHub Action Run
Source Files on build 36111420941
  • Tree
  • List 1015
  • Changed 6
  • Source Changed 0
  • Coverage Changed 6
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #36111420941
  • ff2817dd on github
  • Prev Build on main (#36110233399)
  • Next Build on main (#36115353196)
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