Fix documentation link to no-self-update feature#4795
Merged
FranciscoTGouveia merged 1 commit intorust-lang:mainfrom Apr 1, 2026
Merged
Fix documentation link to no-self-update feature#4795FranciscoTGouveia merged 1 commit intorust-lang:mainfrom
no-self-update feature#4795FranciscoTGouveia merged 1 commit intorust-lang:mainfrom
Conversation
Member
@FranciscoTGouveia Fair point, I'd say maybe just forget about the line number... |
rami3l
approved these changes
Apr 1, 2026
djc
approved these changes
Apr 1, 2026
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
3 participants
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.
While reviewing #3051, I noticed that this link was deprecated.
That said, I would like to point out that whenever
Cargo.tomlis modified (specifically, if lines are added above the current location ofno-self-update), the link will break again.I am not sure if there is a reliable way to prevent this, but I wanted to highlight it as a potential issue going forward.