Repository navigation
Conversation
The previous pin (4e80c37e, gno @ 2025-09-29) can no longer unmarshal current upstream package-server responses, causing every branch's CI to fail with: amino: unrecognized concrete type full name vm.InvalidPackageError Root cause: gno upstream PR #5357 (commit 6d40b3207, 2026-03-25) registers `vm.InvalidPackageError` / `vm.InvalidFileError` in the gno CLI's amino codec. Before that, the CLI couldn't decode the typed errors that `vm.QueryFile` started returning after #4410 (gnomod.toml v2). The v1.1.0 release branch (96264d21d, 2026-04-01) is the gnoland1.1 chain release but does NOT include #5357 (release branches don't get CLI tooling backports automatically). v1.1.0 is correct for chain runtime but wrong for CLI tooling. Master HEAD (5111dbc2 @ 2026-05-11) includes #5357 plus 6 weeks of stabilization. This is the smallest pin that produces working CI today. Trade-off vs picking a tagged release: master HEAD isn't a release tag, so it could shift if we re-bumped naively. The pin is a 40-char SHA, so it's immutable in practice. If/when gno ships a release line that backports #5357, switch to that. Unblocks gnodaokit#62 (security audit v5 realm fixes) and any future PR.
ea6983c to
6bba257
Compare
|
v2 CI ran (gno-test, gno-lint) — error type changed but still fails. Progress confirmed: Before this bump ( The CLI couldn't decode the typed errors at all. PR #5357 fixed this. After this bump ( The CLI now correctly decodes the error and surfaces TWO underlying issues:
Both are deeper than this PR's scope (one-line SHA bump). Parking this investigation — the bump itself is the right direction (closes the amino decode bug, gets us a meaningful error message), but the gnomod.toml / local-discovery side needs a separate look. Won't block gnodaokit#62 in the meantime — it's Draft, awaiting a secondary CODEOWNERS reviewer per Memba v7.1 Phase 1 protocol. CI red is acknowledged; we'll come back to it. |
|
Superseded by #71, which repins the toolchain to This proposes |
Summary
Bumps
GNOVERSIONin the Makefile from4e80c37e(gno @ 2025-09-29) to5111dbc2(gno master HEAD @ 2026-05-11).Root cause
Every branch's CI was failing with:
This is fixed upstream by gno PR #5357 (commit
6d40b3207, 2026-03-25), which registersvm.InvalidPackageError/vm.InvalidFileErrorin the gno CLI's amino codec. Before that, the CLI couldn't decode the typed errors thatvm.QueryFilestarted returning after #4410 (gnomod.toml v2 introduced typed errors invm/qfileABCI responses).Last green CI on
mainwas 2025-11-12 (run19292629043/19292629044); no main commits since masked the rot.Why this specific commit (and not v1.1.0)
I tried
96264d21d(v1.1.0/chain/gnoland1.1, 2026-04-01) first — that's the gno commit running ongnoland1, so it mirrors deployed-chain behaviour. It did not work (CI run). Reason: the v1.1.0 release branch is for the chain runtime, not the CLI tooling. PR #5357 fixed a CLI/codec issue and was not backported to the v1.1 release line — only master has it.5111dbc2= gnomasterHEAD as of today (2026-05-11). Includes #5357 plus 6 weeks of stabilization. Subject:fix(tm2): add duplicate peer protection (#5319).Trade-off vs picking a tagged release:
v1.1.1orv1.2.0), switch to that for stability symmetry with the chain.Diff
One-line change.
Test plan
gno-lintjob green on this PRgno-testjob green on this PRHistory
4e80c37e→96264d21d(v1.1.0). Failed: lacks #5357.4e80c37e→5111dbc2(master HEAD with #5357). Force-pushed.Notes