It's necessary every so often to bump the (pinned) nightly toolchain used in CI, often due to breaks elsewhere in the ecosystem. This can result in major headaches from accumulated changes and lints that are necessary to address.
One approach I've seen is to automate a PR every so often that bumps the nightly version in order to see the effects on CI. From there, a human can check to see what (if anything) needs to be done manually before merging. Here's an example of this in action.
It would be useful to investigate adding such functionality to the repository.
It's necessary every so often to bump the (pinned) nightly toolchain used in CI, often due to breaks elsewhere in the ecosystem. This can result in major headaches from accumulated changes and lints that are necessary to address.
One approach I've seen is to automate a PR every so often that bumps the nightly version in order to see the effects on CI. From there, a human can check to see what (if anything) needs to be done manually before merging. Here's an example of this in action.
It would be useful to investigate adding such functionality to the repository.