Greptile Summary

Reviewed PR #432 which fixes CI by hardcoding https://ethereum.publicnode.com as PROVIDER_MAINNET instead of using the secrets.MAINNET_PROVIDER || fallback expression that was silently consuming a stale Infura secret on push runs.

Confidence Score: 5/5

Safe to merge — the one-line change is targeted, low-risk, and directly addresses the confirmed CI regression.

The diff is a single-line replacement that removes a secret reference in favour of a hardcoded public URL. The logic is straightforward, the root cause is well-evidenced in the PR description, and the only remaining item (stale comment on line 79) is a non-blocking style nit.

No files require special attention.

Important Files Changed

_{Reviews (1): Last reviewed commit: "fix(ci): ignore stale mainnet secret in ..." | Re-trigger Greptile}

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (dev/v4-fin@b2eb3a0). Learn more about missing BASE report.

@@              Coverage Diff              @@
##             dev/v4-fin     #432   +/-   ##
=============================================
  Coverage              ?   58.83%           
=============================================
  Files                 ?       12           
  Lines                 ?     1834           
  Branches              ?        0           
=============================================
  Hits                  ?     1079           
  Misses                ?      755           
  Partials              ?        0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Confirmed the mainnet regression is fixed here.

• PR run 23620730825 now uses PROVIDER_MAINNET: https://ethereum.publicnode.com, and test (v1, mainnet), test (v2, mainnet), and test (v3, mainnet) all pass.
• The only remaining red check is test (v3, arbitrum), and it is the same broader failure we already saw on dev/v4-fin after fix(ci): replace rate-limited Infura with public RPC #431 (23619459609 on 2026-03-26): the forked trade setup in tests/test_uniswap.py is reverting on Arbitrum (test_assets / test_make_trade*).

I am not broadening this PR to paper over that unrelated Arbitrum failure. This PR does the narrow thing it was opened for: stop push runs from preferring the stale mainnet secret.

Addressed Greptile's P2 nit (3f73505): updated stale comment on line 79 to reflect that all provider env vars are now hardcoded public endpoints (no longer "use secret if available").

Everything else is unchanged — Greptile 5/5, mainnet CI green, Arbitrum failure is pre-existing and unrelated.