How to replace cosmossdk.io packages

[marcello33]

Hello,

I have forked a specific version of cosmos-sdk, on top of which I am building my own project.

In my project repo, I am using github.com/cosmos/cosmos-sdk as a dependency, which I can then replace with my fork, with
github.com/cosmos/cosmos-sdk => github.com/my-org/cosmos-sdk v1.0.0

Lately, some modules in the upstream cosmos-sdk have been provided with their own go.mod and release cycles, and moved to the cosmossdk.io registry. Hence, in my sdk fork, to force the usage of my own packages, in every go.mod of needed modules, I am replacing the package with the directory path.
For example, for upgrade module, I have
replace cosmossdk.io/x/upgrade => ../x/upgrade.

So far so good.
The thing tho is that - to build on top of the forked version of the sdk - my project will also need to import some cosmossdk.io packages, out of the forked sdk control. An example of my project root go.mod could be

module github.com/my-org/my-project

go 1.22.1

require (
	cosmossdk.io/api v0.7.2
	cosmossdk.io/x/tx v0.12.0
	github.com/cosmos/cosmos-sdk v0.50.1
)


replace (
	github.com/cosmos/cosmos-sdk => github.com/my-org/cosmos-sdk v1.0.0
)

The question is: how can I obtain the same behaviour for the following packages?

	cosmossdk.io/api v0.7.2
	cosmossdk.io/x/tx v0.12.0

I basically want to use github.com/my-org/cosmos-sdk/x/tx instead of cosmossdk.io/x/tx v0.12.0 and github.com/my-org/cosmos-sdk/api instead of cosmossdk.io/api v0.7.2

Thanks

[julienrbrt]

In that case github.com/my-org/cosmos-sdk/x/tx needs to be its own go module named cosmossdk.io/x/tx.
You don't have to tag it, but then you can just replace it like replace cosmossdk.io/x/tx => github.com/my-org/cosmos-sdk/x/tx.
Same goes for any other of our modules.

[marcello33]

Thanks @julienrbrt, I was struggling understanding the versions to be used with that replace directive, as go was complaining with replacement module without version must be directory path and I didn't want to tag all of them.
Ended up using the stable branch from my-org/my-repo and the relative version was fetched automatically on go mod tidy.
Thanks, closing it.