Closed rhamzeh closed 3 months ago
➜ testing-ground GOPROXY=direct go get -u github.com/d-jeffery/go-lib-test
go: downloading github.com/d-jeffery/go-lib-test v0.2.0-java
go: upgraded github.com/d-jeffery/go-lib-test v0.1.3-go => v0.2.0-java
➜ testing-ground GOPROXY=direct go get github.com/d-jeffery/go-lib-test@v0.1.5-go
go: downloading github.com/d-jeffery/go-lib-test v0.1.5-go
go: downgraded github.com/d-jeffery/go-lib-test v0.2.0-java => v0.1.5-go
➜ testing-ground GOPROXY=direct go get github.com/d-jeffery/go-lib-test@latest
go: upgraded github.com/d-jeffery/go-lib-test v0.1.5-go => v0.2.0-java
➜ testing-ground GOPROXY=direct go get github.com/d-jeffery/go-lib-test@v0.1.5-go
go: downgraded github.com/d-jeffery/go-lib-test v0.2.0-java => v0.1.5-go
➜ testing-ground GOPROXY=direct go get -u github.com/d-jeffery/go-lib-test
go: upgraded github.com/d-jeffery/go-lib-test v0.1.5-go => v0.2.0-java
➜ testing-ground GOPROXY=direct go get -u github.com/d-jeffery/go-lib-test@v0.1.2-js
go: downloading github.com/d-jeffery/go-lib-test v0.1.2-js
go: downgraded github.com/d-jeffery/go-lib-test v0.2.0-java => v0.1.2-js
➜ testing-ground GOPROXY=direct go get -u github.com/d-jeffery/go-lib-test
go: upgraded github.com/d-jeffery/go-lib-test v0.1.2-js => v0.2.0-java
➜ testing-ground go list -m -versions github.com/d-jeffery/go-lib-test
github.com/d-jeffery/go-lib-test v0.1.0-go v0.1.1-go v0.1.2-js v0.1.3-go v0.1.5-go v0.2.0-java
➜ testing-ground GOPROXY=direct go get github.com/d-jeffery/go-lib-test@v0.2.0-go
go: downloading github.com/d-jeffery/go-lib-test v0.2.0-go
go: downgraded github.com/d-jeffery/go-lib-test v0.2.0-java => v0.2.0-go
We would like to publish the different packages to their respective registries, for that we're gonna have to setup a publish process that works for a mono repo.
First is investigating if we can publish a particular package if a tag with an identifier is pushed, e.g.
v0.1.0-js
tag publishesv0.1.0
of the js package to npmv0.2.1-java
tag publishesv0.2.1
of the java package to mavencentralAs go treats any tag as a release, it will treat the above as releases too, but let's still push
vx.x.x-go
tags and use those for goInvestigate whether https://github.com/changesets/changesets can be helpful in this case, otherwise we'll need to build the tooling ourselves.
/pkg/go/v0.x.x
works!