Update to Cadence v1.9.7 #952
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,16 +1,16 @@ | ||
| module github.com/onflow/flow-evm-gateway/integration | ||
|
|
||
| go 1.25.1 | ||
|
Contributor
There was a problem hiding this comment. 🧩 Analysis chain🏁 Script executed: # First, check the current Go version configuration in the repo
find . -name "go.mod" -type f | head -20Repository: onflow/flow-evm-gateway Length of output: 90 🏁 Script executed: # Look at the CI configuration to understand current Go version
cat .github/workflows/ci.yml | head -50Repository: onflow/flow-evm-gateway Length of output: 906 🏁 Script executed: # Check if there are other Go version specifications in the repo
rg "go\s+1\." --type yaml --type toml | head -20Repository: onflow/flow-evm-gateway Length of output: 49 🌐 Web query:
💡 Result: Go 1.25.1 (2025–2026): release availability + compatibilityAvailability (when/where)
Compatibility (what it runs on / what changes to expect)
Practical takeaway for 2026: If you’re choosing a Go version for 2026, Go 1.25.1 exists and is usable, but you generally want the latest Go 1.25.x available at the time (for cumulative security/bug fixes). [1][4] 🌐 Web query:
💡 Result:
Go 1.25 specifically
What to do
Sources: GitHub issue tracking Go 1.25 support and build-version rule [1], official FAQ on supported Go versions / build-version relationship [2], install docs warning about local source builds and recommending binaries [3]. [1] golangci/golangci-lint#5873 🌐 Web query:
💡 Result: Yes—GitHub Actions can run Go 1.25.1, but you should install it via
Minimal workflow snippet: steps:
- uses: actions/checkout@v5
- uses: actions/setup-go@v6
with:
go-version: '1.25.1'
- run: go versionSources: [1] [3] [2] Synchronize CI Go version with tests/go.mod requirement. The CI workflow currently specifies 🤖 Prompt for AI Agents |
||
|
|
||
| require ( | ||
| github.com/ethereum/go-ethereum v1.16.8 | ||
| github.com/goccy/go-json v0.10.4 | ||
| github.com/onflow/cadence v1.9.7 | ||
| github.com/onflow/crypto v0.25.4 | ||
| github.com/onflow/flow-emulator v1.16.3 | ||
| github.com/onflow/flow-evm-gateway v0.0.0-20240201154855-4d4d3d3f19c7 | ||
| github.com/onflow/flow-go v0.45.0-internal-rc.3.0.20260129222115-cc0505f2afd5 | ||
| github.com/onflow/flow-go-sdk v1.9.13 | ||
|
Comment on lines
+8
to
+13
Contributor
There was a problem hiding this comment. 🧩 Analysis chain🏁 Script executed: cat tests/go.modRepository: onflow/flow-evm-gateway Length of output: 13905 🌐 Web query:
💡 Result: I couldn’t find any So there are no “v1.16.3 release notes” or “v1.16.3 breaking changes” for `onflow/flow-emulator, because that release tag doesn’t appear to exist. If you meant a different tag (e.g., Sources 🌐 Web query:
💡 Result:
What’s changed (high level)
Full changelog compare range: Citations:
🌐 Web query:
💡 Result: For
Cadence v1.9.7 itself also does not list any breaking changes in its release notes (it lists a bug-fix port plus dependency/merge housekeeping). [2] Sources: [1] [2] 🌐 Web query:
💡 Result:
What changed in the
Note: The repo’s tags page shows References: 🌐 Web query:
💡 Result: I couldn’t find any GitHub “Release” entry (i.e., release notes text) for onflow/atree v0.12.1—it appears to be published as a tagged module version without accompanying GitHub release notes. What I can confirm from public sources:
How to see the actual changes: use GitHub’s tag comparison view for the atree repo (compare Sources
Citations:
🌐 Web query:
💡 Result:
Practical ways to get the “release notes” locally: # see the exact latest version your environment resolves
go list -m -json golang.org/x/exp@latest
# list changes between the last two published pseudo-versions
git clone https://go.googlesource.com/exp
cd exp
git log --oneline e25ba8c21ef6..716be5621a96Sources: [1], [2] 🌐 Web query:
💡 Result:
Issue #243 is titled: “darwin/arm64: checkptr panic in _unixModeBit when using race detector.” [2] Sources: [1] [2] 🌐 Web query:
💡 Result: I couldn’t find any upstream release notes (or even evidence of an existing tag) for What I can confirm from public registries is:
If you do have
To get authoritative “release notes” for exactly Sources: [1], [2] 🌐 Web query:
💡 Result: The onflow/flow-emulator versions available on GitHub are published as tags (and partially as “Releases”). Most recent tags (newest → older):
More older tags (examples):
For the full list, use the repository’s Tags page. (github.com) Citations:
🌐 Web query:
💡 Result: I couldn’t find any official release/tag If you’re trying to confirm whether git ls-remote --tags https://github.com/onflow/flow-emulator.git | grep v0.16.3Also note: the emulator is typically consumed via the Flow CLI (it’s bundled/distributed with the CLI), so you may need to pin a Flow CLI version rather than an emulator version. [2] Sources: 🌐 Web query:
💡 Result:
I could not find any public reference to a tag/release If you’re trying to verify whether go list -m -versions modernc.org/libcand/or check what your dependency graph selected: go mod graph | grep modernc.org/libcSources: pkg.go.dev module page (repo mapping) [1]; Socket package index (latest version shown) [2]. 🏁 Script executed: # Check if we can find more details about the atree changes and verify the versions against pkg.go.dev
curl -s https://pkg.go.dev/github.com/onflow/atree@v0.12.1 2>/dev/null | grep -i "version\|release" | head -10 || echo "Could not fetch pkg.go.dev"Repository: onflow/flow-evm-gateway Length of output: 781 Verify modernc.org/libc version and review pre-release/unpublished dependency changes. Most versions are confirmed available, but Additionally, note that:
🤖 Prompt for AI Agents |
||
| github.com/rs/zerolog v1.34.0 | ||
| github.com/stretchr/testify v1.11.1 | ||
| golang.org/x/sync v0.19.0 | ||
|
|
@@ -22,7 +22,7 @@ require ( | |
| cloud.google.com/go/auth/oauth2adapt v0.2.8 // indirect | ||
| cloud.google.com/go/compute/metadata v0.9.0 // indirect | ||
| cloud.google.com/go/iam v1.5.3 // indirect | ||
| cloud.google.com/go/kms v1.24.0 // indirect | ||
| cloud.google.com/go/longrunning v0.7.0 // indirect | ||
| github.com/DataDog/zstd v1.5.6-0.20230824185856-869dae002e5e // indirect | ||
| github.com/Microsoft/go-winio v0.6.2 // indirect | ||
|
|
@@ -154,9 +154,9 @@ require ( | |
| github.com/multiformats/go-multistream v0.6.0 // indirect | ||
| github.com/multiformats/go-varint v0.0.7 // indirect | ||
| github.com/munnerz/goautoneg v0.0.0-20191010083416-a7dc8b61c822 // indirect | ||
| github.com/ncruces/go-strftime v1.0.0 // indirect | ||
| github.com/olekukonko/tablewriter v0.0.5 // indirect | ||
| github.com/onflow/atree v0.12.1 // indirect | ||
| github.com/onflow/fixed-point v0.1.1 // indirect | ||
| github.com/onflow/flow-core-contracts/lib/go/contracts v1.9.2 // indirect | ||
| github.com/onflow/flow-core-contracts/lib/go/templates v1.9.2 // indirect | ||
|
|
@@ -234,7 +234,7 @@ require ( | |
| go.uber.org/zap v1.27.0 // indirect | ||
| go.yaml.in/yaml/v2 v2.4.2 // indirect | ||
| golang.org/x/crypto v0.46.0 // indirect | ||
| golang.org/x/exp v0.0.0-20251023183803-a4bb9ffd2546 // indirect | ||
| golang.org/x/net v0.48.0 // indirect | ||
| golang.org/x/oauth2 v0.34.0 // indirect | ||
| golang.org/x/sys v0.39.0 // indirect | ||
|
|
@@ -255,10 +255,10 @@ require ( | |
| gopkg.in/yaml.v3 v3.0.1 // indirect | ||
| gotest.tools v2.2.0+incompatible // indirect | ||
| lukechampine.com/blake3 v1.4.1 // indirect | ||
| modernc.org/libc v1.67.6 // indirect | ||
| modernc.org/mathutil v1.7.1 // indirect | ||
| modernc.org/memory v1.11.0 // indirect | ||
| modernc.org/sqlite v1.44.3 // indirect | ||
| nhooyr.io/websocket v1.8.7 // indirect | ||
| ) | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: onflow/flow-evm-gateway
Length of output: 90
🏁 Script executed:
Repository: onflow/flow-evm-gateway
Length of output: 13503
🌐 Web query:
github.com/onflow/cadence v1.9.7 release notes breaking changes💡 Result:
Cadence v1.9.7 release notes (released Jan 29, 2026) do not list any breaking changes. The release is a small patch with:
No “Breaking changes” / “Migration” section is present in the v1.9.7 release notes. [1] [2]
Sources: [1] [2]
🌐 Web query:
github.com/onflow/flow-go v0.45.0 release notes breaking changes💡 Result:
github.com/onflow/flow-gov0.45.0 (pre-release, Jan 29, 2026) calls out this breaking change in the release notes:#8307). This may break any components/tests that relied on the previous wire/serialization distinction between anilpayload vs an empty[]byte{}(e.g., hashing, signing, equality checks, or byte-level protocol compatibility). [1]Potential “soft” breaking change to watch for (not explicitly labeled as breaking, but can affect callers/tools):
#8109) — update any scripts/configs/CLI usage or internal references that still use the old terminology. [1]Source: flow-go v0.45.0 release notes/commit list. [1]
[1] (newreleases.io)
Citations:
🌐 Web query:
github.com/onflow/flow-go-sdk v1.9.13 release notes breaking changes💡 Result:
github.com/onflow/flow-go-sdkv1.9.13 does not list any breaking changes in its release notes. The release contains only a dependency bump:flow-goversion to latest from HCU #989) and nothing else is called out. [1]flow-goversion to latest from HCU #989). [2]Conclusion: No breaking changes are documented for flow-go-sdk v1.9.13; it appears to be a patch release updating Cadence. [1]
Sources: [1] [2]
🌐 Web query:
github.com/onflow/atree v0.12.1 release notes💡 Result:
onflow/atree v0.12.1 — Release notes (Jan 29, 2026)
#624(ported fromonflow/atree-internal#17). [1]Sources:
[1] (github.com)
Citations:
🌐 Web query:
cloud.google.com/go/kms v1.24.0 release notes💡 Result:
I wasn’t able to find a publicly indexed changelog/release-notes entry that lists what changed specifically in
cloud.google.com/go/kms v1.24.0.What I can confirm from public sources:
cloud.google.com/go/kms v1.24.0was published on Jan 15, 2026. [1]If you need the exact v1.24.0 change list, it should be in the repo’s tag artifacts (typically
kms/CHANGES.mdfor thekms/v1.24.0tag) and/or the GitHub release page for that tag, but those pages weren’t retrievable via search in the sources I found.Sources: [1] [2] [3]
🌐 Web query:
github.com/onflow/crypto v0.25.4 release notes💡 Result:
github.com/onflow/cryptodoes not have a GitHub “Release” entry for v0.25.4 (it exists as a tag, not a published release with detailed notes). The tag metadata indicates:v0.25.46848f9b(github.com)Citations:
Verify flow-go v0.45.0-internal-rc.3 payload encoding changes and compatibility.
This version introduces a breaking change: "Normalize nil payload value encoding to empty slice" (
#8307). This affects wire format/serialization and may impact hashing, signing, equality checks, or byte-level protocol compatibility. Review code that relies on nil vs empty[]byte{}distinction and update tests accordingly.Additionally, "scheduled callbacks" have been renamed to "transactions" (
#8109) — verify any internal references use the updated terminology.Other upgrades are safe:
Note: cloud.google.com/go/kms v1.24.0 changelog is not publicly documented; unable to verify for breaking changes.
🤖 Prompt for AI Agents