chore: Rust toolchain/CI update and workspace setup #2830
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 Git ↗︎
|
Riateche
force-pushed
the
workspace-and-lints
branch
from
1a7fbc8 to
c8a3120
Compare
ali-behjati
approved these changes
Jul 4, 2025
lazer/contracts/solana/clippy.toml
Outdated
| @@ -0,0 +1,3 @@ | |||
| allow-unwrap-in-tests = true | |||
| allow-expect-in-tests = true | |||
| #allow-indexing-slicing-in-tests = true | |||
keyvankhademi
approved these changes
Jul 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
actions-rust-lang/setup-rust-toolchainSwatinem/rust-cacheas the above action calls it internallySmart contracts remain in their separate workspaces. There are a couple of reasons why they cannot be included in the main workspace (pinned dependencies, lack of chain tooling support, different release profile configs).
Rationale
How has this been tested?