Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: rename PRIVATE_ALCHEMY_KEY to NEXT_PRIVATE_ALCHEMY_KEY #1097

Merged
merged 1 commit into from
Sep 17, 2024

Conversation

agualis
Copy link
Contributor

@agualis agualis commented Sep 17, 2024

Using NEXT prefix simplifies setup of vitest integration tests.
Note the name of the env var in github secrets remains the same (PRIVATE_ALCHEMY_KEY)

Copy link

vercel bot commented Sep 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
frontend-v3 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 17, 2024 10:17am
test-v3 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 17, 2024 10:17am

@garethfuller garethfuller merged commit cbfee00 into main Sep 17, 2024
7 checks passed
@garethfuller garethfuller deleted the fix/renameAlchemyKey branch September 17, 2024 10:25
agualis added a commit that referenced this pull request Sep 17, 2024
garethfuller added a commit that referenced this pull request Sep 18, 2024
* feat: adapt V2 and V3 buildCall parameters in handlers

* chore: improve comment

* chore: improve comment2

* chore: add NEXT prefix to NEXT_PRIVATE_ALCHEMY_KEY for simpler local integration test setup (#1097)

* chore: rename function

* chore: Update template

---------

Co-authored-by: Gareth Fuller <[email protected]>
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.

2 participants