Repository navigation
feat: add Cargo executable path setting in 0.1.1 - #2
Merged
Merged
Conversation
Mucheen
marked this pull request as ready for review
October 22, 2026 07:03
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
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.
Adds a native Cargo executable file setting in both the plugin Settings tab and the Cargo build settings page. Empty values retain discovery; explicit paths are shared by metadata and task execution, and the selected directory is placed first on PATH for companion tools.
Prepares preview 0.1.1 with
buildSystems: 2/settings: 2and pins host compatibility to 1lck/Lithe-IDEA#1420 (a972d4204ce4c178d0314872119c11db8d435341). SDK inputs remain byte-identical at that revision. Old hosts retain compatible 0.1.0 through Store filtering; published 0.1.0 assets remain unchanged.Validation: all 11 tests pass using the verified pinned Core bridge, including real metadata/build/check/test/run/clean through an executable path with spaces, package immutability, and refusal by an older host. SDK hashes, tag/version consistency and packaging pass. Native settings render correctly in light and dark appearance; marketplace update acceptance follows publication.