It'll fail to apply, and complain that a newer version is already set (i.e in the require section). This is a bit of a strange implementation by the upstream project.
To address, we should drop the check that looks for a newer version in the go.mod, if the version is set in the 'replaces' block
I agree it looks like a weird configuration for their dependencies. I believe if we could allow setting only the replaces block in gobump this issue could be solved as well.
Example:
Upstream have set this in the 'replace' section:
And they also have this in the 'require' section:
If you try doing this using go/bump:
It'll fail to apply, and complain that a newer version is already set (i.e in the require section). This is a bit of a strange implementation by the upstream project.
To address, we should drop the check that looks for a newer version in the go.mod, if the version is set in the 'replaces' block