Skip to content

Remove stale client secret config#1240

Closed
rossgalloway wants to merge 1 commit into
release/26-04-17from
codex/remove-stale-secret-env
Closed

Remove stale client secret config#1240
rossgalloway wants to merge 1 commit into
release/26-04-17from
codex/remove-stale-secret-env

Conversation

@rossgalloway

@rossgalloway rossgalloway commented May 19, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Remove stale client-exposed Alchemy, Infura, and Clusters API env examples.
  • Simplify the legacy Wagmi config module to only expose the registered runtime config.
  • Keep Clusters identity lookup using the public API endpoint without API key/header plumbing.

Validation

  • bun run lint:fix
  • bun run tslint
  • bun run build

Remove unused client-exposed provider key env entries and simplify the legacy Wagmi config module to only retain the registered runtime config. Keep Clusters lookup public without API-key header plumbing.
@vercel

vercel Bot commented May 19, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
yearnfi Ready Ready Preview, Comment May 19, 2026 9:32pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
yearnfi-nextjs Ignored Ignored May 19, 2026 9:32pm

Request Review

@github-actions

github-actions Bot commented May 19, 2026

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@rossgalloway

Copy link
Copy Markdown
Collaborator Author

Closing this PR because it has been superseded by the grouped remediation flow.

The browser-exposed key cleanup is now covered by the grouped Browser-exposed service keys remediation.

Replacement:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant