Dependency upgrades and other maintenance #412
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.
I have not tested this (nor am I certain how to best do that). Much more straight-forward than my failed rustix PRs though.
I'm happy with rebasing this over time if keeping up with the ecosystem is not currently a priority. (I just like doing this sort of work and had fs-err
File::options
on my todo > got that merged today > I checked out where it would be useful > foundOpenOptions
usage in this repo > found more dependencies that were not at the latest version > found an unnecessarily large unsafe block while upgrading nix)