This repository was archived by the owner on Sep 4, 2024. It is now read-only.
chore: bump lambda version to pick up new Zora secret #426
Conversation
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
jsy1218
requested review from
ConjunctiveNormalForm,
zhongeric,
marktoda,
hensha256 and
codyborn
as code owners
ConjunctiveNormalForm
approved these changes
May 23, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I forgot to ask someone to add the ZORA JSON RPC URL into secret, before merging. Now I have to bump the lambda version so that the URA pipeline can pick up the new secret. I manually retried the entire URA beta stage, but still it can't find the secret: