update release tags #622
Description
The current release tagging scheme (v13, v14, v15, etc.) is incompatible with Go's semantic import versioning requirements. Go modules with major version >1 require the version suffix in the module path (e.g., github.com/zeta-chain/protocol-contracts-evm/v15), but our go.mod declares:
module github.com/zeta-chain/protocol-contracts-evm
This forces downstream consumers (like zeta-node) to use workaround pseudo-versions with an outdated base tag:
require github.com/zeta-chain/protocol-contracts-evm v1.0.2-athens3.0.20260106080948-62189c92b766
This works functionally but:
- Looks confusing/stale in dependency lists
- Requires maintaining special v1.0.x-athens3 tags
- Makes it unclear which actual release a commit corresponds to
Proposed Solution
Adopt the v0.x versioning scheme
| Current | Proposed |
|---|---|
| v16.0.0 | v0.16.0 |
| v17.0.0 | v0.17.0 |