Repository navigation
chore: remove Lava testnet support - #67
Merged
Merged
Conversation
The Lava testnet (lava-testnet-2) is being sunset, so the explorer no
longer builds, deploys or links to a testnet variant of itself.
Workflows:
- build.yml / publish.yml: build-web and publish-web matrix is now
[mainnet] only; the NEXT_PUBLIC_NETWORK build-arg is dropped. The
mainnet path is unchanged: same GitHub environment, same
info-web:mainnet-<sha> / mainnet-latest tags, same cache scope.
- deploy.yml: testnet removed from the environment choice.
- ci.yml: push trigger no longer includes the testnet branch.
Web:
- Header.tsx / MobileNav.tsx: Mainnet/Testnet toggle removed.
- lib/network.ts deleted (no remaining imports).
- Dockerfile: NEXT_PUBLIC_NETWORK ARG/ENV removed (only reader was
network.ts).
API: Swagger description no longer mentions Testnet.
Docs: CLAUDE.md and .claude/rules/frontend.md no longer describe the
toggle.
Intentionally kept: LAV1 ("Lava Testnet") in packages/shared chains.ts
and chain-icons, so historical relay data per spec stays readable.
Not covered here (infra, handled separately): the GitHub `testnet`
environment and its secrets, ECR info-web:testnet-* images, the
info-testnet ECS cluster, and the testnet-* hostname.
The Lava testnet chain (lava-testnet-2, spec LAV1) is shutting down, so the explorer no longer needs a display name or icon alias for it.
nimrod-teich
marked this pull request as ready for review
November 10, 2026 09:33
nimrod-teich
approved these changes
Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The Lava testnet is being shut down. This repo built, deployed and linked to a testnet variant of the explorer. After this change the explorer is mainnet-only.
What changed
Workflows
build.yml,publish.yml: thebuild-web/publish-webmatrix is now[mainnet]only. TheNEXT_PUBLIC_NETWORKbuild-arg is removed.deploy.yml:testnetremoved from theenvironmentchoice.ci.yml: push trigger no longer includes thetestnetbranch.Web
Header.tsx,MobileNav.tsx: the Mainnet/Testnet toggle is removed. The surrounding containers keep the same classes and gaps.apps/web/src/lib/network.tsdeleted. It was the only reader ofNEXT_PUBLIC_NETWORKand nothing else imported it.apps/web/Dockerfile:NEXT_PUBLIC_NETWORKARG/ENV removed.API and docs
CLAUDE.mdand.claude/rules/frontend.mdno longer describe the toggle.LAV1 chain entry
LAV1: "Lava Testnet"removed from the display-name map inpackages/shared/src/constants/chains.ts.lav1removed from the icon aliases inpackages/shared/src/utils/chain-icons.ts, and its assertion fromchain-icons.test.ts. The Lava testnet chain itself is going away, so nothing will need these labels.What is intentionally unchanged
mainnet, image tagsinfo-web:mainnet-<sha>andmainnet-latest, cache scopeweb-mainnet. The only difference is that the build-arg which no code reads anymore is gone.Verification
git grep -i lav1finds nothing.pnpm typecheckpasses;pnpm testpasses (shared 44, web 19, api 134).@/lib/network,IS_TESTNET,isTestnet,getToggleUrl; JSX balanced; YAML valid.Not covered here (infra, handled separately after approval)
testnetand its secrets/vars (AWS_ROLE_ARN,NEXT_PUBLIC_API_URL).testnetgit branch (CI used to trigger on it).info-web:testnet-*images and theweb-testnetGHA cache scope.info-testnet(servicesapi,web, task definitionsinfo-testnet-api/info-testnet-web) and its IAM role.testnet-*hostname, and anyCORS_ORIGINSentry for the testnet web origin.