Conversation
* Bump next from 15.5.7 to 15.5.9 (0xsequence#944) Bumps [next](https://github.com/vercel/next.js) from 15.5.7 to 15.5.9. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v15.5.7...v15.5.9) --- updated-dependencies: - dependency-name: next dependency-version: 15.5.9 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * Pin foundry to v1.5.0 instead of nightly (0xsequence#947) * Include repo and extras in syncpack config to ensure deps are synced (0xsequence#945) * Include repo and extras in syncpack config to ensure deps are synced across all * Updating support deps * Updating deps * Updating pnpm lock * Fixing type errors within wdk tests * Short circuit 404s (0xsequence#949) * skip witness on signers that don't support it * add passkey to test * 3.0.0-beta.6 --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Taylan Pince <taylanpince@gmail.com> Co-authored-by: Corban Riley <corbanbrook@gmail.com> Co-authored-by: Agusx1211 <agusgit@pm.me>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
|
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Sorry @Dargon789, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Summary of ChangesHello @Dargon789, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request marks a new beta release for the 0xsequence SDK, bringing substantial enhancements to user data management, optimizing dapp client performance, and rectifying issues within the Apple authentication process. These updates aim to provide developers with more robust tools for handling user-specific data and to improve the overall efficiency and reliability of decentralized application connections. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces a significant number of updates across multiple packages, primarily version bumps for a new beta release. Key changes include a major expansion of the userdata service API, the addition of caching for signed calls in the dapp-client, and fixes related to Apple authentication. My review has identified a potential high-severity regression where automatic session refresh for expired signers was removed, and a medium-severity bug in the validation logic for creating explicit session configurations. Overall, the changes are substantial and move the project forward, but these two points should be addressed to ensure stability and correctness.
I am having trouble creating individual review comments. Click here to see my feedback.
packages/wallet/dapp-client/src/ChainSessionManager.ts (814-826)
The automatic session refresh logic for expired signers has been removed. This could be a regression, as it previously provided a seamless user experience by handling expired session errors automatically. Was this removal intentional? If this automatic refresh is no longer handled elsewhere, consider re-introducing this mechanism to avoid disrupting user flows.
packages/wallet/dapp-client/src/utils/index.ts (153-155)
The permission validation here is incomplete. It only checks params.permissions, but doesn't account for permissions generated from nativeTokenSpending. This will cause an error to be thrown incorrectly if params.permissions is empty but nativeTokenSpending.allowedRecipients is provided. The validation should check that the total number of permissions is greater than zero.
if (params.permissions.length === 0 && (params.nativeTokenSpending?.allowedRecipients?.length ?? 0) === 0) {
throw new Error('createExplicitSessionConfig: At least one permission is required.')
}
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
No description provided.