Update atproto packages #308
Merged
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
vercel
bot
temporarily deployed
to
Preview – frontpage-oauth-preview-client
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.
This also fixes an issue in atproto-browser where records with blob refs weren't validating because the
BlobRefwas a different version to the one used internally in@atproto/lexicons.I think there's also a bug in next.js here because I had to bump @lpm/core to the same version of @atproto/lexicons otherwise the transitive version would be picked up by next.js...
In any case, we only have one version of that now in the whole monorepo which fixes the problem.
This is a followup on 85d8969 that had this same cause but that commit only fixed it for rendering blob refs, not validating records containing blob refs.