set Zod to be explicitly 3.22.4 to solve infinite depth error#134
Merged
staceysv merged 1 commit intoapi_key_headersfrom Mar 24, 2025
Merged
set Zod to be explicitly 3.22.4 to solve infinite depth error#134staceysv merged 1 commit intoapi_key_headersfrom
staceysv merged 1 commit intoapi_key_headersfrom
Conversation
Contributor
|
looks great, thank you, let's try it! |
staceysv
approved these changes
Mar 24, 2025
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
2 participants
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.
1. What is the goal of this PR?
hot-fix for api_key_headers branch
2. What specific parts of T3C are you changing and how?
Every package.json now explicitly has the same version.
3. How did you test these changes?
Red squiggly line go away
Please add one or more reviewer(s) and tag them in a new post in the Slack dev channel :)