1 Commits (ed4c357976aff489a5dd7134f505e0c1afe0390b)

Author	SHA1	Message	Date
Mantas-M	096aeff13e	feat: Splitting `rust` workspace into `main` and `sealevel` (#4438) ... ### Description The single rust workspace has been split into 2 workspaces. The sealevel workspace includes the contents of the previous `sealevel` folder and the main workspace includes everything else. The workspaces differ in rust versions as the sealevel has the old one to ensure compatability, the main workspace has and updated `rustc` version of `1.80.1`. Some dependencies and sub-dependencies have been locked in versions of the old pre-split workspace to ensure no breaking code changes. The rust CI workflow has been updated to include both workspaces in the tests. ### Drive-by changes N/A ### Related issues Relates to https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4361 ### Backward compatibility No. ### Testing Rust Unit tests from the CI	3 months ago
Noah Bayindirli 🥂	ba946f1eff	fix(config): switch to recommended 'rust-analyzer' from deprecated 'cargo' (#3886) ... ### Description - switch to recommended `rust-analyzer` since `cargo` is deprecated	6 months ago
webbhorn	61f270aec5	Fix publisher for rust-analyezr extension. (#496) ... Without this change, vscode emits a warning that maktlad.rust-analyzer is not in the extensions marketplace. Since May 16, rust-lang is the new publisher for the rust-analyzer extension: https://twitter.com/rust_analyzer/status/1526181089391280128?cxt=HHwWgICwgazniq4qAAAA	3 years ago
Yorke Rhodes	1d572ba887	Add vscode workspaces and settings (#387) ... * Add recommended root extensions * Add typescript and solidity workspace settings * Add rust settings and extensions * Update some root settings * Comment unused rust vars as revealed by analyzer * Remove root extensions in favor of workspace * Update README with VSCode hint	3 years ago