Update and pin neon sdk and add an error logging escape hatch #39
Conversation
This file contains 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
brettimus
force-pushed
the
fix-neon-auth-flow
branch
from
75222e6 to
8eee227
Compare
|
just released 1.3.2 from this branch to resolve the issue |
keturiosakys
approved these changes
Jan 24, 2025
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.
There were issues with (at least for me and @Nlea) doing the authorized Neon CLI flow. We could log in, but project branches would never show up.
Turns out it had to do with an update to the neon api sdk. Not sure why pnpm resolved the sdk differently than npm (for me), but I figured this would be a good time to: