-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Rust: add rust-analyzer update instructions
#20404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds comprehensive documentation for updating rust-analyzer dependencies in the Rust CodeQL implementation. The changes provide step-by-step instructions for maintaining rust-analyzer and related dependencies, including toolchain updates and schema migrations.
- Adds a detailed section on rust-analyzer update procedures
- Includes instructions for dependency management, bazel file regeneration, and toolchain updates
- Documents the complete workflow from upgrade to testing and schema migration
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
redsun82
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, apart from a minor oversight coming from me 🙂
|
The CI failures should go away with the merge from main I just did |
Co-authored-by: Simon Friis Vindum <paldepind@github.com>
paldepind
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Instructions are clear and easy to follow. Thanks @geoffw0 and @redsun82.
One thought going forward, in #20408 I ran into a problem because the first cargo upgrade also applies to ruby/extractor/Cargo.toml and that broke the Ruby extractor. I guess it would be preferable if we could update RA for the Rust extractor without affecting the Ruby extractor.
Fair point, although it is a nice side effect that the Ruby extractor is kept up to date as well. |
|
Merging - but I'm happy to make further changes to these instructions if there are more suggestions. |
First commit (most of the work) is taken from closed PR #19930 by @redsun82 .
I hope to add a few more details before this is ready to merge.