You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
which means that every time i update my fork, i need to update the directive and retrigger the update with go mod tidy
What did you expect to see?
replace directive should not mutate. To be precise, I expect them to be immutable in all situations because they're hand made directives to instruct to tool where and which versions of the code to pick
What did you see instead?
replace directive mutates.
The text was updated successfully, but these errors were encountered:
The go.mod file is intended to provide reproducible builds. A branch that may move is (by definition) not reproducible, so this is working as designed.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I'm trying to test a personal fork of a dependency in a project, and i'm using the replace directive as follows:
For some reason, when i run
go mod tidy
to update the deps, the replace directive is mutated replacing it with the actual commit hashwhich means that every time i update my fork, i need to update the directive and retrigger the update with
go mod tidy
What did you expect to see?
replace directive should not mutate. To be precise, I expect them to be immutable in all situations because they're hand made directives to instruct to tool where and which versions of the code to pick
What did you see instead?
replace directive mutates.
The text was updated successfully, but these errors were encountered: