Foundry v1.5.0 instead of nightly (0xsequence#947) (#134)

[Dargon789]

No description provided.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[sourcery-ai]

Sorry, we are unable to review this pull request

The GitHub API does not allow us to fetch diffs exceeding 300 files, and this pull request has 770

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist¹! 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 implements a substantial architectural shift, transitioning the project's monorepo management to turbo and lefthook, and re-architecting the core wallet SDK to a new v3 structure. It also introduces new Next.js applications for documentation and web interfaces, alongside general updates to development tooling and CI/CD pipelines. The changes aim to modernize the build system, streamline development workflows, and lay the groundwork for the next major version of the Sequence wallet SDK.

Highlights

• Monorepo Tooling Migration: The project has transitioned from preconstruct and custom scripts to turbo for monorepo management, significantly updating package.json scripts and introducing lefthook for git hooks to streamline development workflows.
• Core Library Re-architecture (v3): The previous 0xsequence core package and several sub-packages (abi, account, api, auth, core) have been removed. The project is now structured around new v3 core libraries such as @0xsequence/wallet-primitives, @0xsequence/wallet-core, and @0xsequence/wallet-wdk, indicating a major re-architecture of the wallet SDK.
• Build and CI/CD Enhancements: GitHub Actions for dependency installation have been updated to use newer Node.js (v20) and PNPM (v10) versions, along with actions/cache v4. ESLint and Prettier configurations have been simplified, and a new .github/CODEOWNERS file has been added for better code ownership management.
• New Next.js Applications: Two new Next.js applications, docs and web, have been introduced under an extras/ directory. These applications come with their own configurations, basic page structures, and associated assets, suggesting an expansion of the project's web presence and documentation.
• Changeset Management Update: The .changeset/config.json has been updated to a newer schema (3.0.5), and several new changeset files have been added, detailing a series of patch releases and a beta release for v3 across various @0xsequence and @repo packages.

Ignored Files

• Ignored by pattern: .github/workflows/** (3)
  • .github/workflows/on_pr_pnpm-format-label.yml
  • .github/workflows/pnpm-format.yml
  • .github/workflows/tests.yml

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request represents a significant and impressive overhaul of the repository's tooling and structure. The migration to Turborepo, pnpm, Changesets, and Lefthook modernizes the development workflow and improves maintainability. The project structure has been simplified by refactoring numerous packages into a more cohesive architecture under packages/wallet and packages/services. The configuration updates across the board, from ESLint and Prettier to GitHub Actions, are well-executed and follow modern best practices. I've added a couple of minor suggestions to improve the new configuration, but overall, this is an excellent and well-thought-out refactoring effort.