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
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.
pushing a v0.1.0-js tag publishes v0.1.0 of the js package to npm
pushing a v0.2.1-java tag publishes v0.2.1 of the java package to mavencentral
As 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 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!The text was updated successfully, but these errors were encountered: