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
Select "Create a new tag on publish" and type v1.0.0-athens3 (note the v)
Click "Publish release"
Users can install this package with yarn add @zetachain/protocol-contracts@athens3.
To release a new athens3 version repeat the process above with an incremented minor or patch version, for example, v1.0.1-athens3.
To release a new stable version repeat the process above using a version without a tag, for example, v1.0.0.
Users can install this package with yarn add @zetachain/protocol-contracts.
I propose we release under athen3 as often as possible, so that other tasks can be unblocked. Right now I have to rely on a locally linked protocol-contracts package, which is much less convenient than a tagged version on npm.
The text was updated successfully, but these errors were encountered:
@andresaiello as there are multiple packages depending on
@zetachain/protocol-contracts
being ready for Athens 3, I propose the following.Let's publish this package under an
athens3
tag on npm.This could be as simple as adding the following workflow:
https://github.com/zeta-chain/networks/blob/8613fa8406a5a739dc3318a0f98306a6b408d05d/.github/workflows/publish-npm.yaml
After this workflow is added, to publish under an
athens3
tag:v1.0.0-athens3
(note thev
)Users can install this package with
yarn add @zetachain/protocol-contracts@athens3
.To release a new
athens3
version repeat the process above with an incremented minor or patch version, for example,v1.0.1-athens3
.To release a new stable version repeat the process above using a version without a tag, for example,
v1.0.0
.Users can install this package with
yarn add @zetachain/protocol-contracts
.I propose we release under
athen3
as often as possible, so that other tasks can be unblocked. Right now I have to rely on a locally linked protocol-contracts package, which is much less convenient than a tagged version on npm.The text was updated successfully, but these errors were encountered: