Repository navigation
v1.4.0
v1.4.0
Coordinated upgrade — halt height 113000 (GovDAO proposal #5), halt block time 2026-09-17T13:24:04Z. halt_min_version as proposed: (empty).
Released from chain/mainnet at 00417a1be. Previous release: v1.3.0.
Docker images: ghcr.io/gnolang/gno/gnoland:v1.4.0, …/gnokey:v1.4.0, …/gnoweb:v1.4.0, …/gno:v1.4.0, …/gnodev:v1.4.0, …/gnofaucet:v1.4.0, …/gnocontribs:v1.4.0, …/gpao:v1.4.0 — digests in UPGRADES.md.
Binaries: attached below (gno, gnokey, gnoland, gnoweb, gnodev × linux/darwin × amd64/arm64), built by the release / chain-tag workflow from this tag; CHECKSUMS.txt covers all of them. Each prints v1.4.0 on version.
Changes since v1.3.0 (compare):
- Consensus-relevant: the crossing
curparameter becomes a fixed binding (#6193) - Node: a release tag can gate a chain upgrade —
halt_min_versionparsing,gnoland version, release tooling (#6177) - Docs: #6184, #6175, #6156; deployment docs
01c5ff8f7,139a63fe6,00417a1be
Tagged retroactively on 2026-09-22. The network moved to this code at the halt above, running the chain-mainnet image sha-00417a1 (sha256:805d723bcd2938ac42d3056f70d11a2f50ee89ca852c618f6aee60fe1bfd79ad; a pull between 12:50 and 12:56 UTC got sha-139a63f, identical Go code) — the same code, reporting an unparseable version. This tag gives that state a version; from v1.6.0 on, releases are tagged before they run.