-
-
Notifications
You must be signed in to change notification settings - Fork 50
Perform semver-incompatible dependency updates; squash CI warnings #947
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
base: master
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 11882144096Details
💛 - Coveralls |
A manual audit of the existing expr specifiers didn't turn up any problems with just switching to the 2024 semantics. https://doc.rust-lang.org/nightly/edition-guide/rust-2024/macro-fragment-specifiers.html
Inform Clippy of our minimum supported Rust version, so it won't advise us to use #[expect] (which is too new). We don't support older Rust because of cargo:: syntax in build.rs: error: the `cargo::` syntax for build script output instructions was added in Rust 1.77.0, but the minimum supported Rust version of `git-interactive-rebase-tool v2.4.1 (/home/bgilbert/sw/git-interactive-rebase-tool)` is 1.56.0. Switch to the old `cargo:rustc-check-cfg=cfg(allow_unknown_lints)` syntax (note the single colon). See https://doc.rust-lang.org/cargo/reference/build-scripts.html#outputs-of-the-build-script for more information about build script outputs.
This doesn't change whether the fields are accessible outside the crate, and avoids clippy warnings: warning: scoped visibility modifier on a field --> src/input/key_bindings.rs:44:2 | 44 | pub(crate) action_drop: Vec<Event>, | ^^^^^^^^^^ | = help: consider making the field private and adding a scoped visibility method for it = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#field_scoped_visibility_modifiers
It doesn't seem possible to disable the warning with an outer attribute, and using an inner attribute would cause inconsistent linting across files. Just disable the warning everywhere; presumably when we exclude code from test builds we do it intentionally. https://rust-lang.github.io/rust-clippy/master/index.html#cfg_not_test
Upstream breaking change: `\n` is now treated as width 1.
CI is clean; ready for review. |
Hey @bgilbert , thank you for all the effort that you've put into this pull request, as well as the other pull requests you've put up. Sadly, some of the changes I've made recently conflict with some of the work you've done. My plan is to cherry-pick over several of your changes over the next little while, since multiple of your changes are still very valid. |
No problem! I have some experience with maintainer burnout too, and you should do whatever is needed for your own health and, only after that, for the health of the project. Thanks for building and maintaining GIRT! |
Perform semver-incompatible dependency updates of captur, claims, crossterm, git2, unicode-width, and version-track. unicode-width now treats
\n
as having width 1.Disable compiler warning for Rust 2021
expr
fragment specifiers. A manual audit of the existingexpr
specifiers didn't turn up any problems with just switching to the 2024 semantics.Fix clippy warnings. Set MSRV to avoid more clippy warnings. Reformat with latest Rust nightly.