-
Notifications
You must be signed in to change notification settings - Fork 695
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: version packages #2204
Merged
Merged
chore: version packages #2204
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
0d907b7
to
dca5476
Compare
dca5476
to
1850262
Compare
1850262
to
f263b00
Compare
f263b00
to
62344fa
Compare
62344fa
to
522b065
Compare
DanielSinclair
approved these changes
Oct 15, 2024
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 PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@rainbow-me/[email protected]
Minor Changes
f02bced: The Authentication API now supports ERC-1271 and ERC-6492 for smart contract signature verification to enable Sign-in with Ethereum for Smart Contract Wallets, including Coinbase Smart Wallet and Argent.
We have also deprecated the
siwe
andethers
peer dependencies in favor ofviem/siwe
to make RainbowKit even more seamless.No changes are necessary for dApps that don't rely on the Authentication API.
Follow the appropriate steps below to migrate.
** NextAuth Authentication **
siwe
andethers
rainbowkit-siwe-next-auth
, andviem
This allows
viem
to verify smart contract signatures.const config = getDefaultConfig({ /* your config */ }); + const publicClient = config.getClient().extend(publicActions);
authorize
implementation in/api/auth/[...nextauth].ts
Reference the with-next-siwe-next-auth example for more guidance.
** Custom Authentication **
siwe
andethers
viem
This allows
viem
to verify smart contract signatures.const config = getDefaultConfig({ /* your config */ }); + const publicClient = config.getClient().extend(publicActions);
createAuthenticationAdapter
implementationgenerateSiweNonce
parseSiweMessage
andverifyMessage
if your Verify handlerReference the with-next-siwe-iron-session example for more guidance.
@rainbow-me/[email protected]
Minor Changes
f02bced: The Authentication API now supports ERC-1271 and ERC-6492 for smart contract signature verification to enable Sign-in with Ethereum for Smart Contract Wallets.
We have also deprecated the
siwe
andethers
peer dependencies in favor ofviem/siwe
.Follow the appropriate steps below to migrate.
siwe
andethers
rainbowkit-siwe-next-auth
, andviem
This allows
viem
to verify smart contract signatures.const config = getDefaultConfig({ /* your config */ }); + const publicClient = config.getClient().extend(publicActions);
authorize
implementation in/api/auth/[...nextauth].ts
Reference the with-next-siwe-next-auth example for more guidance.
Patch Changes
@rainbow-me/[email protected]
Patch Changes
wagmi
to^2.12.17
@rainbow-me/[email protected]
Patch Changes
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17
[email protected]
Patch Changes
wagmi
to^2.12.17