NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #1746 by repository stars
Latest stable
v1.7.0
Last release 13 days ago
09 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Most releases are documented
notes for 9 of 11 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
1502 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
…a new homepage, realm pages as markdown, and security fixes on file paths and links. The full list is in #6426.
A coordinated upgrade. Every mainnet validator halts at block 1183000, around 09:05 UTC on 2026-10-30, set by GovDAO proposal 15, and restarts on v1.7.0: after the halt a node refuses an older binary, and before it this one (halt_min_version = v1.7.0). Cut on the same commit as v1.7.0-rc.1, which onyx runs since block 754001.
Released from chain/mainnet at e4c2e7d9f. Previous release: v1.5.1, which mainnet runs: mainnet skipped v1.6.0 (#6372), so v1.7.0 also carries its changes. Every release mainnet has run is in its upgrade ledger.
Who should run it: every mainnet validator, at the halt. Pull the image or download the binary now; keep running v1.5.1 until the halt, and leave halt_height at 0 in config.toml.
New since v1.6.0:
:.gno test -p is capped at GOMAXPROCS.From v1.6.0, which mainnet skipped:
sanitize.Block* escapes <gno-button anywhere on a line, and gnoweb draws <gno-button /> as a call-to-action link.v1.5.1 running and halt_height at 0 in config.toml; let the node halt, then restart it on this release.-ipfs-gateway (default https://ipfs.filebase.io; a reverse proxy that sets its own CSP must allow it), -canonical-origin, -index-community (default none), -trusted-paths, -no-realm-notice (the notice is on by default), -trusted-proxies, -no-index (never on mainnet), -indexer-url (empty: off). Aliases no longer chain. Move gnoweb after the halt, with the new static homepage (misc/deployments/home-alias/home.mainnet.md): its buttons are only safe behind the new sanitizer.-web-ipfs-gateway and -validator-key-file.Multi-arch (linux/amd64, linux/arm64), signed keylessly by the release / docker workflow, the index and each platform image.
| Image | Index digest |
|---|---|
ghcr.io/gnolang/gno/gnoland:v1.7.0 |
sha256:6145f2bebebe24ae798ae5ffb5f2f348bfd70c538e6b3722152e8643b2880cb3 |
ghcr.io/gnolang/gno/gnoweb:v1.7.0 |
sha256:78b1701335c89e525254cd7e996cce4b808c4d95e5273e127c78fd1bda399f0f |
ghcr.io/gnolang/gno/gnofaucet:v1.7.0 |
sha256:18e1d5314b7cb8158afd74af23abecbe53aef9c45bc342c5daf952a35d7a6cb3 |
ghcr.io/gnolang/gno/gnokey:v1.7.0 |
sha256:62ee18e2e3dd74823e829507d567589949596de25336b0193daecd80155ff421 |
ghcr.io/gnolang/gno/gno:v1.7.0 |
sha256:5ab582a5cc3392186fc4cdc434f6347f0ee5b6e1166fe1bdcac4591cf2ff4347 |
ghcr.io/gnolang/gno/gnodev:v1.7.0 |
sha256:c129bfadebf57f1e54ab4a009ea497495aceac2d980b12eb048873b95077fa3c |
ghcr.io/gnolang/gno/gnocontribs:v1.7.0 |
sha256:ae9bd1aeeccf42d2a6ff5cc8e8bc23df101e06eab8bb86c6fa6a428e5cc7c5c8 |
ghcr.io/gnolang/gno/gpao:v1.7.0 |
sha256:e5484d887d99ba0848a79ef7da4b01c3e2410c52b42973c21f1924ec98ae8372 |
Attached below: gno, gnokey, gnoland, gnoweb and gnodev for linux and darwin, amd64 and arm64, built by the release / chain-tag workflow from this tag. CHECKSUMS.txt covers all of them, and gnoland, gnokey and gno print v1.7.0 on version. The binaries and CHECKSUMS.txt carry a build-provenance attestation.
gh attestation verify gnoland_linux_amd64 --repo gnolang/gno \
--signer-workflow gnolang/gno/.github/workflows/release-chain-tag.yml \
--source-ref refs/tags/v1.7.0
# cosign v3 or later: the signatures are in the Sigstore bundle format
cosign verify ghcr.io/gnolang/gno/gnoland:v1.7.0 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity https://github.com/gnolang/gno/.github/workflows/release-docker.yml@refs/tags/v1.7.0
Compare. Every commit is a cherry-pick from master; the full list, with what was left out and why, is in #6426.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Release candidate for `v1.7.0`, a coordinated upgrade. Onyx runs this candidate. Mainnet gets v1.7.0, cut on this same commit once onyx has run the ca
Release candidate for v1.7.0, a coordinated upgrade. Onyx runs this candidate. Mainnet gets v1.7.0, cut on this same commit once onyx has run the candidate without issue.
Released from chain/mainnet at e4c2e7d9f. Previous release: v1.5.1, which mainnet runs; onyx moves from v1.6.0-rc.1. Mainnet skipped v1.6.0, so v1.7.0 also carries its changes (#6372). Every release onyx has run is in its upgrade ledger.
Who should run it: onyx operators; mainnet operators need nothing yet. At the halt after block 754000 (GovDAO proposal #35, about 2026-10-29 12:51 UTC), every onyx validator restarts on this release; before that height, a node refuses this binary.
New since v1.6.0-rc.1, which onyx runs:
:; deposits and the genesis loader attribute a key to the realm before its first colon.gno test -p is capped at GOMAXPROCS.set-halt.sh refuses a floor the network already meets. No node code.Mainnet also takes v1.6.0's changes, which onyx runs since v1.6.0-rc.1: see its notes.
halt_height at 0 in config.toml, let the node halt, then restart on this release.-ipfs-gateway, default https://ipfs.filebase.io (Filebase's free public gateway); empty turns the rewrite off. gnoweb refuses to start on a gateway that is not https (http on loopback only), carries credentials, a path or a query, or sits on the chain domain, the canonical origin's host or a subdomain of either. CSP img-src drops https://ipfs.io and https://cloudflare-ipfs.com and adds the gateway; a reverse proxy that sets its own CSP must allow the gateway too. Move gnoweb after the halt.-web-ipfs-gateway, same default.VERSION=v1.7.0-rc.1: the candidate shares its commit with v1.7.0, which git describe would name.Multi-arch (linux/amd64, linux/arm64), signed keylessly by the release / docker workflow, the index and each platform image.
| Image | Index digest |
|---|---|
ghcr.io/gnolang/gno/gnoland:v1.7.0-rc.1 |
sha256:76d132a22044b32c88c7c07e478dd21bbffe26268565819c1ac12b87c6df9fc7 |
ghcr.io/gnolang/gno/gnoweb:v1.7.0-rc.1 |
sha256:0d5983d07baa44d08a2751131e934e79cae1bb23e765806a7b13df066352e120 |
ghcr.io/gnolang/gno/gnofaucet:v1.7.0-rc.1 |
sha256:ebad7a9137467751a3633873b045d8d0107fb73b827fbb63482859e93e9cfb92 |
ghcr.io/gnolang/gno/gnokey:v1.7.0-rc.1 |
sha256:635a21a82a7a0a966109dd72db7ebe279e236d529f5cc302d348dd7afa2aeced |
ghcr.io/gnolang/gno/gno:v1.7.0-rc.1 |
sha256:b80d0bd094d7096c22103af8a14ecf9a1a9888033c45ce1c3954e5d417f7bca3 |
ghcr.io/gnolang/gno/gnodev:v1.7.0-rc.1 |
sha256:edddbde03a057ee5c11098ab71a6b485a3ce01753df49c14fe0b2427cf65507f |
ghcr.io/gnolang/gno/gnocontribs:v1.7.0-rc.1 |
sha256:748c8ae8d86d3de295183504cb54514dd084412574be0d427d2805468c9b67e4 |
ghcr.io/gnolang/gno/gpao:v1.7.0-rc.1 |
sha256:6263dfb156e1a684dbc3d5e30a71cc3a9de543bb510207fcceec2462452bbb9a |
Attached below: gno, gnokey, gnoland, gnoweb and gnodev for linux and darwin, amd64 and arm64, built by the release / chain-tag workflow from this tag. CHECKSUMS.txt covers all of them, and gnoland, gnokey and gno print v1.7.0-rc.1 on version. The binaries and CHECKSUMS.txt carry a build-provenance attestation.
gh attestation verify gnoland_linux_amd64 --repo gnolang/gno \
--signer-workflow gnolang/gno/.github/workflows/release-chain-tag.yml \
--source-ref refs/tags/v1.7.0-rc.1
# cosign v3 or later: the signatures are in the Sigstore bundle format
cosign verify ghcr.io/gnolang/gno/gnoland:v1.7.0-rc.1 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity https://github.com/gnolang/gno/.github/workflows/release-docker.yml@refs/tags/v1.7.0-rc.1
Compare. Every commit is a cherry-pick from master; the full list, with what was left out and why, is in #6426.
…(#6293), realm pages as markdown (#5794), and security fixes on file paths and links (#6261, #6296, #6295, #6294).
[!WARNING] Never deployed on mainnet. Do not run this release. Mainnet skips
v1.6.0and goes fromv1.5.1tov1.7.0, which carries these changes and later ones. Onyx runs the same code asv1.6.0-rc.1.The halt height in this tag's message (
848000) was an estimate and never applied: no halt tov1.6.0was scheduled.
A coordinated upgrade. At the halt, every validator restarts on v1.6.0: after the halt a node refuses an older binary, and before it this one (halt_min_version = v1.6.0). Cut on the same commit as v1.6.0-rc.1, which onyx runs.
Released from chain/mainnet at c868ccab1. Previous release: v1.5.1.
Who should run it: nobody. Onyx stays on v1.6.0-rc.1, the same code.
sanitize.Block* escapes <gno-button anywhere on a line, and gnoweb draws <gno-button /> as a call-to-action link.-validator-key-file.halt_height at 0 in config.toml, let the node halt, then restart on this release.-canonical-origin (set it to https://gno.land), -index-community (default none), -trusted-paths, -no-realm-notice (the notice is on by default), -trusted-proxies (empty: X-Forwarded-Host is ignored), -no-index (never on mainnet), -indexer-url (empty: off). Aliases no longer chain. Move gnoweb after the halt, with the new static homepage (misc/deployments/home-alias/home.mainnet.md).Multi-arch (linux/amd64, linux/arm64), signed keylessly by the release / docker workflow, the index and each platform image.
| Image | Index digest |
|---|---|
ghcr.io/gnolang/gno/gnoland:v1.6.0 |
sha256:c884ef4357dab61bb9d836a447d53149fd5d67530e83c302e687705c5077306d |
ghcr.io/gnolang/gno/gnoweb:v1.6.0 |
sha256:6663a1244b0da74cbb829d4ece7ae60a8c2166dc92cb84ef1610c8cfd8e56449 |
ghcr.io/gnolang/gno/gnofaucet:v1.6.0 |
sha256:1168c43fca716ed33a0283785f31456dfc3b6ecc1e69590d4ec868623a330cfe |
ghcr.io/gnolang/gno/gnokey:v1.6.0 |
sha256:157174797649eb12e2db9754672a55ada5949c0d1d2af7d43aea46cd661b7c6c |
ghcr.io/gnolang/gno/gno:v1.6.0 |
sha256:bd018c38478b263a03e4ebdcb563c139d0a47db9b5bcefb52e2fe811ff70d178 |
ghcr.io/gnolang/gno/gnodev:v1.6.0 |
sha256:b47708831a92802066b6ac83ffe4aade08edcac99332d43d8e1025a05e564aa0 |
ghcr.io/gnolang/gno/gnocontribs:v1.6.0 |
sha256:0176a991accf1509912b3481bc3815b2b9af6277a5035017d2326664327de3ae |
ghcr.io/gnolang/gno/gpao:v1.6.0 |
sha256:3ab27f3045107f58859451d6104f947fe11bc784346ae47fa496c70f8dfbb211 |
Attached below: gno, gnokey, gnoland, gnoweb and gnodev for linux and darwin, amd64 and arm64, built by the release / chain-tag workflow from this tag. CHECKSUMS.txt covers all of them, and gnoland, gnokey and gno print v1.6.0 on version. The binaries and CHECKSUMS.txt carry a build-provenance attestation.
gh attestation verify gnoland_linux_amd64 --repo gnolang/gno \
--signer-workflow gnolang/gno/.github/workflows/release-chain-tag.yml \
--source-ref refs/tags/v1.6.0
# cosign v3 or later: the signatures are in the Sigstore bundle format
cosign verify ghcr.io/gnolang/gno/gnoland:v1.6.0 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity https://github.com/gnolang/gno/.github/workflows/release-docker.yml@refs/tags/v1.6.0
Compare. Every commit is a cherry-pick from master; the full list, with what was left out and why, is in #6372.
Release tooling on chain/mainnet since v1.5.1: #6335 (full CI on chain PRs, one docker run per tag) and the deployment docs corrections reviewed in #6323.
…(#6293), realm pages as markdown (#5794), and security fixes on file paths and links (#6261, #6296, #6295, #6294).
Release candidate for v1.6.0, a coordinated upgrade. Onyx runs this candidate. Mainnet skips v1.6.0: these changes reach it in v1.7.0.
Released from chain/mainnet at c868ccab1. Previous release: v1.5.1. Recorded in the upgrade ledger.
Who should run it: onyx operators; mainnet operators need nothing. At the halt after block 445000 (GovDAO proposal #33, about 2026-10-16 13:04 UTC), every onyx validator restarts on this release; before that height, a node refuses this binary.
sanitize.Block* escapes <gno-button anywhere on a line, and gnoweb draws <gno-button /> as a call-to-action link.-validator-key-file.halt_height at 0 in config.toml, let the node halt, then restart on this release.-canonical-origin, -index-community (default none), -trusted-paths, -no-realm-notice (the notice is on by default), -trusted-proxies (empty: X-Forwarded-Host is ignored), -no-index (never on mainnet), -indexer-url (empty: off). Aliases no longer chain. Move gnoweb after the halt, with the new static homepage (misc/deployments/home-alias/home.testnet.md).VERSION=v1.6.0-rc.1: the candidate shares its commit with v1.6.0, which git describe would name.Multi-arch (linux/amd64, linux/arm64), signed keylessly by the release / docker workflow, the index and each platform image.
| Image | Index digest |
|---|---|
ghcr.io/gnolang/gno/gnoland:v1.6.0-rc.1 |
sha256:4286ffcd805f7a4925cc15ad2290d4be0e1c28f63436bf7b0ed4570ff38e7e38 |
ghcr.io/gnolang/gno/gnoweb:v1.6.0-rc.1 |
sha256:870f7e397322ebafa60057a410b374b5ce84ce94f56a0f69b4b27bb868cd5878 |
ghcr.io/gnolang/gno/gnofaucet:v1.6.0-rc.1 |
sha256:d7b5c534f551d6f820c396e91bfcb8936f06ebac0dc14b367fee2fd69c944789 |
ghcr.io/gnolang/gno/gnokey:v1.6.0-rc.1 |
sha256:b088b37ded6f619f584aa68328bd4a2aa8b1fa379f73742fe4fc33d33c8610de |
ghcr.io/gnolang/gno/gno:v1.6.0-rc.1 |
sha256:99d09b4d7b49dccbf26e728e088f8aa7f2d1fe7be04308438e009855771991be |
ghcr.io/gnolang/gno/gnodev:v1.6.0-rc.1 |
sha256:812e71889056b6efbed83ca2fae33c39d80710cbdbec45fa34b0bbbbfe7396f8 |
ghcr.io/gnolang/gno/gnocontribs:v1.6.0-rc.1 |
sha256:e9f1bbbc58b586fb7e4aea2c9fb9f8edf38e13e2b3efbcacd17435fb4b536301 |
ghcr.io/gnolang/gno/gpao:v1.6.0-rc.1 |
sha256:16e6526c5e09738fb256ded141273600572ceef692d7a52ecf49eb7af1408e39 |
Attached below: gno, gnokey, gnoland, gnoweb and gnodev for linux and darwin, amd64 and arm64, built by the release / chain-tag workflow from this tag. CHECKSUMS.txt covers all of them, and gnoland, gnokey and gno print v1.6.0-rc.1 on version. The binaries and CHECKSUMS.txt carry a build-provenance attestation.
gh attestation verify gnoland_linux_amd64 --repo gnolang/gno \
--signer-workflow gnolang/gno/.github/workflows/release-chain-tag.yml \
--source-ref refs/tags/v1.6.0-rc.1
# cosign v3 or later: the signatures are in the Sigstore bundle format
cosign verify ghcr.io/gnolang/gno/gnoland:v1.6.0-rc.1 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity https://github.com/gnolang/gno/.github/workflows/release-docker.yml@refs/tags/v1.6.0-rc.1
Compare. Every commit is a cherry-pick from master; the full list, with what was left out and why, is in #6372.
Release tooling on chain/mainnet since v1.5.1: #6335 (full CI on chain PRs, one docker run per tag) and the deployment docs corrections reviewed in #6323.
Nothing published for this version
Nothing published for this version
A rolling patch. No halt, no GovDAO proposal, no version floor: nothing nodes agree on changes, so each operator switches whenever convenient. Cut on
A rolling patch. No halt, no GovDAO proposal, no version floor: nothing nodes agree on changes, so each operator switches whenever convenient. Cut on the same commit as v1.5.1-rc.1, which onyx ran first.
Released from chain/mainnet at 07e44776c. Previous release: v1.5.0. Recorded in the mainnet upgrade ledger as a rolling release.
Who should run it: mainnet operators, whenever convenient. Nodes on v1.5.0 and v1.5.1 run the same chain and peer with each other, so validators can move one at a time. Onyx stays on v1.5.1-rc.1, the same code.
Cherry-picked from master; the p2p and faucet code is identical to master's.
replacing connection to resolve a simultaneous open is normal.p2p.persistent_peers lists the same peer ID twice, only the last address is dialed, with a warning at startup.max_num_outbound_peers no longer blocks persistent peers, even at 0. They still count toward it.Multi-arch (linux/amd64, linux/arm64), signed keylessly by the release / docker workflow, the index and each platform image.
| Image | Index digest |
|---|---|
ghcr.io/gnolang/gno/gnoland:v1.5.1 |
sha256:810c3d57395dbe85d34b02b2df7b711a400f2b04dcfa9e94e34f9ca53d1f2290 |
ghcr.io/gnolang/gno/gnoweb:v1.5.1 |
sha256:ba8836f151f1a5000dbd8241aa4a87b4e0f56b36aa2abb829fc6752ac890ddba |
ghcr.io/gnolang/gno/gnofaucet:v1.5.1 |
sha256:d936676915a7d70b1b8334f3565e0b7c72416df4192da5fb85d7c2156c32a045 |
ghcr.io/gnolang/gno/gnokey:v1.5.1 |
sha256:dfc24980f30122b90f824d15a054600cf8dcffbf8af22c1eb52da7863597aa59 |
ghcr.io/gnolang/gno/gno:v1.5.1 |
sha256:2dafa995935fc7eb3ef5b42c40972007c1244cdeec2c21c62a7defd7b938b832 |
ghcr.io/gnolang/gno/gnodev:v1.5.1 |
sha256:aca6f52ff0b0f85a36efb794b676e03439468843dab2317c2a3deaf895744ef3 |
ghcr.io/gnolang/gno/gnocontribs:v1.5.1 |
sha256:7cd37f1791852171f66f7b8f70c1323a01272ae7abe163aacc58c326fc2a77ee |
ghcr.io/gnolang/gno/gpao:v1.5.1 |
sha256:f1b2cfb7c67c39fbbc0eacbc248eec155bd07c45235635b261cf3be3e3437219 |
Attached below: gno, gnokey, gnoland, gnoweb and gnodev for linux and darwin, amd64 and arm64, built by the release / chain-tag workflow from this tag. CHECKSUMS.txt covers all of them, and gnoland, gnokey and gno print v1.5.1 on version. The binaries and CHECKSUMS.txt carry a build-provenance attestation.
gh attestation verify gnoland_linux_amd64 --repo gnolang/gno \
--signer-workflow gnolang/gno/.github/workflows/release-chain-tag.yml \
--source-ref refs/tags/v1.5.1
# cosign v3 or later: the signatures are in the Sigstore bundle format
cosign verify ghcr.io/gnolang/gno/gnoland:v1.5.1 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity https://github.com/gnolang/gno/.github/workflows/release-docker.yml@refs/tags/v1.5.1
Compare. Node and service code:
waitForDialTime (test only, #6067)Release tooling and docs on chain/mainnet since v1.5.0, no node code: the release model and upgrade ledger (#6228), the rolling ledger kind (#6245), signed and attested release artifacts with a daily ledger check (#6243), and the onyx deployment folder (#6244).
Release candidate for `v1.5.1`, a rolling patch. No halt, no GovDAO proposal, no version floor: nothing nodes agree on changes, so each operator switc
Release candidate for v1.5.1, a rolling patch. No halt, no GovDAO proposal, no version floor: nothing nodes agree on changes, so each operator switches whenever convenient. Onyx runs this candidate since 2026-10-13. Mainnet runs v1.5.1, cut on this same commit after onyx ran the candidate without issue.
Released from chain/mainnet at 07e44776c. Previous release: v1.5.0.
Who should run it: onyx operators. Mainnet operators run v1.5.1 instead: the same code, with the final version string.
Cherry-picked from master; the p2p and faucet code is identical to master's.
replacing connection to resolve a simultaneous open is normal.p2p.persistent_peers lists the same peer ID twice, only the last address is dialed, with a warning at startup.max_num_outbound_peers no longer blocks persistent peers, even at 0. They still count toward it.Multi-arch (linux/amd64, linux/arm64), signed keylessly by the release / docker workflow, the index and each platform image.
| Image | Index digest |
|---|---|
ghcr.io/gnolang/gno/gnoland:v1.5.1-rc.1 |
sha256:231eedbda83b527a900ecbbd79d634dbea3150d3acc93da0c41e1cb63c48e606 |
ghcr.io/gnolang/gno/gnoweb:v1.5.1-rc.1 |
sha256:2b6e33cb53849cc7fa7315670400785ed346e4520ace707e44b55b38290cf37b |
ghcr.io/gnolang/gno/gnofaucet:v1.5.1-rc.1 |
sha256:9748479d28230e8f1bf440aae5100d58475a63002adb0dc0e57b96ee83d5c362 |
ghcr.io/gnolang/gno/gnokey:v1.5.1-rc.1 |
sha256:239a0f2c97d7969929e8ad481af5384f3bd6c3a746f6d2a5e3409a87f95edacd |
ghcr.io/gnolang/gno/gno:v1.5.1-rc.1 |
sha256:cc0e81ad64723671a701f53849d26f84bc5d363a9b1ec8fff1c246af5b9857d6 |
ghcr.io/gnolang/gno/gnodev:v1.5.1-rc.1 |
sha256:8fd1aee7cfa4309c6f5e129d2cafce2581976eff887cf705b21ce99d21af0b3f |
ghcr.io/gnolang/gno/gnocontribs:v1.5.1-rc.1 |
sha256:ced3032b1eb5d4d9e55a7b72f7da8411a00616d00a9a304ffaab770c23459a38 |
ghcr.io/gnolang/gno/gpao:v1.5.1-rc.1 |
sha256:a7a6b73f2577909dfb45f1772d9f59fa77ab40d6ed5e75785b4d305b2798ed17 |
Attached below: gno, gnokey, gnoland, gnoweb and gnodev for linux and darwin, amd64 and arm64, built by the release / chain-tag workflow from this tag. CHECKSUMS.txt covers all of them, and gnoland, gnokey and gno print v1.5.1-rc.1 on version. The binaries and CHECKSUMS.txt carry a build-provenance attestation.
gh attestation verify gnoland_linux_amd64 --repo gnolang/gno \
--signer-workflow gnolang/gno/.github/workflows/release-chain-tag.yml \
--source-ref refs/tags/v1.5.1-rc.1
# cosign v3 or later: the signatures are in the Sigstore bundle format
cosign verify ghcr.io/gnolang/gno/gnoland:v1.5.1-rc.1 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity https://github.com/gnolang/gno/.github/workflows/release-docker.yml@refs/tags/v1.5.1-rc.1
Compare. Node and service code:
waitForDialTime (test only, #6067)Release tooling and docs on chain/mainnet since v1.5.0, no node code: the release model and upgrade ledger (#6228), the rolling ledger kind (#6245), signed and attested release artifacts with a daily ledger check (#6243), and the onyx deployment folder (#6244).
Nothing published for this version
Coordinated upgrade — halt height 162200 (GovDAO proposal #7), halt block time 2026-09-19T10:37:10Z. halt_min_version as proposed: *(empty)*. Released
Coordinated upgrade — halt height 162200 (GovDAO proposal #7), halt block time 2026-09-19T10:37:10Z. halt_min_version as proposed: (empty).
Released from chain/mainnet at e75fef82c. Previous release: v1.4.0.
Docker images: ghcr.io/gnolang/gno/gnoland:v1.5.0, …/gnokey:v1.5.0, …/gnoweb:v1.5.0, …/gno:v1.5.0, …/gnodev:v1.5.0, …/gnofaucet:v1.5.0, …/gnocontribs:v1.5.0, …/gpao:v1.5.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.5.0 on version.
Changes since v1.4.0 (compare):
iota in preprocess (#5981)Tagged retroactively on 2026-09-22. The network moved to this code at the halt above, running the chain-mainnet image sha-e75fef8 (sha256:5b455e5784328aeda1cfa4832e3cb2a58f15f9645c710b8591401bd04c9a900e) — 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.
Coordinated upgrade — halt height 113000 (GovDAO proposal #5), halt block time 2026-09-17T13:24:04Z. halt_min_version as proposed: *(empty)*. Released
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):
cur parameter becomes a fixed binding (#6193)halt_min_version parsing, gnoland version, release tooling (#6177)01c5ff8f7, 139a63fe6, 00417a1beTagged 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.
Coordinated upgrade — halt height 36300 (GovDAO proposal #0), halt block time 2026-09-14T09:17:06Z. halt_min_version as proposed: *(empty)*. Released
Coordinated upgrade — halt height 36300 (GovDAO proposal #0), halt block time 2026-09-14T09:17:06Z. halt_min_version as proposed: (empty).
Released from chain/mainnet at 31b6650a1. Previous release: v1.2.0.
Docker images: ghcr.io/gnolang/gno/gnoland:v1.3.0, …/gnokey:v1.3.0, …/gnoweb:v1.3.0, …/gno:v1.3.0, …/gnodev:v1.3.0, …/gnofaucet:v1.3.0, …/gnocontribs:v1.3.0, …/gpao:v1.3.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.3.0 on version.
Changes since v1.2.0 (compare):
fix(tm2)! (#6173)master's squash of the mainnet deployment folder (#6154) — no code change on this branchTagged retroactively on 2026-09-22. The network moved to this code at the halt above, running the chain-mainnet image sha-31b6650 (sha256:7fffc5ac2d21d6608bed35b31cfc3f2aaefed0d6bb3cdba1d5edbfd905127a3f) — 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.
Nothing published for this version
gnoland-1 genesis, launched 2026-09-12T15:00:00Z. Same commit as the chain/mainnet launch tag.
gnoland-1 genesis, launched 2026-09-12T15:00:00Z. Same commit as the chain/mainnet launch tag.
Launch release of the gno.land mainnet gnoland-1 — genesis at 2026-09-12T15:00:00Z. Cut at the launch commit 9c8eb132e, the same commit as the chain/mainnet tag, which carries genesis.json. No halt: this is the version the chain started on.
Docker images: ghcr.io/gnolang/gno/gnoland:v1.2.0, …/gnokey:v1.2.0, …/gnoweb:v1.2.0, …/gno:v1.2.0, …/gnodev:v1.2.0, …/gnofaucet:v1.2.0, …/gnocontribs:v1.2.0, …/gpao:v1.2.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.2.0 on version.
Changes: see "Changes since pearl" on the chain/mainnet release.
chain/gnoland1.1: fix typeCheckCache stdlib population
chain/gnoland1.1: fix typeCheckCache stdlib population
Hotfix for consensus halt at block 352922 on gnoland1.
Fix: TypeCheckMemPackage wasn't storing 22 leaf stdlibs (time, regexp, math/rand, etc.) in vm.typeCheckCache. This caused non-deterministic gas consumption between fresh and restarted nodes, triggering a consensus halt.
PR: #5400 by @thehowl
Docker (recommended):
docker pull ghcr.io/gnolang/gno/gnoland:gnoland1.1
docker pull ghcr.io/gnolang/gno/gnokey:gnoland1.1
docker pull ghcr.io/gnolang/gno/gnoweb:gnoland1.1
All images: ghcr.io/gnolang/gno/{gnoland,gnokey,gnoweb,gno,gnofaucet,gnodev}:gnoland1.1
From source:
git checkout chain/gnoland1.1
make install # installs gnoland, gnokey, gnoweb, gno
misc/deployments/gnoland1/Full changelog: https://github.com/gnolang/gno/compare/chain/gnoland1.0...chain/gnoland1.1
Nothing published for this version
feat: gnoland1 (betanet) genesis
feat: gnoland1 (betanet) genesis (#5250)
gnoland1 — betanet launch
The first Gno.land betanet. A major milestone between testnet and mainnet: state persistence is guaranteed (resets only in emergencies).
| Field | Value |
|---|---|
| Chain ID | gnoland1 |
| Type | betanet |
| Genesis time | 2026-03-16T09:00:00Z (Mon Mar 16 2026, 10:00 CET) |
| Genesis SHA256 | 97bb99f918d46da375226c9749ba01b5ed1774e0954e225c5f48a9997e7620c6 |
| URL | |
|---|---|
| RPC | https://rpc.betanet.gno.land |
| Web | https://gno.land |
| Faucet | https://faucet.gno.land |
genesis.json — Genesis file for the gnoland1 chaingno.wasm — GnoVM WebAssembly binary (GOOS=js GOARCH=wasm)root.zip — Standard libraries and examples (stdlibs + tests/stdlibs + examples)/r/boards example updates by @edelgado in https://github.com/gnolang/gno/pull/158Full Changelog: https://github.com/gnolang/gno/commits/chain/test1.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.