fix:after compliance applied,the relationship concerning the original one should be omitted #4419
Conversation
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
* make the go module compliant in advance Signed-off-by: Yuntao Hu <[email protected]>
8e39d12 to
03a290e
Compare
Signed-off-by: Yuntao Hu <[email protected]>
BorekZnovustvoritel
approved these changes
Dec 2, 2025
BorekZnovustvoritel
left a comment
There was a problem hiding this comment.
I can confirm that the problem is no longer reproducible with this change. Thank you for addressing it.
spiffcs
approved these changes
Dec 4, 2025
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.
Description
When the replace directive only involving module path is applied, the version is empty ,which means it's non-compliant. Therefore, the compliance needs to be applied ,however,after which the previous non-compliant module entry still exists.
And the problem is that the replace and remove in index.go ignore that IDs of both sides in a relationship need to be compliant.
Type of change
Checklist: