Conversation
turbolent
requested review from
janezpodhostnik,
m-Peter,
peterargue and
zhangchiqing
as code owners
📝 WalkthroughWalkthroughBumps Go version from 1.25.0 to 1.25.1 and upgrades Flow-related dependencies across both Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Tip 🧪 Unit Test Generation v2 is now available!We have significantly improved our unit test generation capabilities. To enable: Add this to your reviews:
finishing_touches:
unit_tests:
enabled: trueTry it out by using the Have feedback? Share your thoughts on our Discord thread! Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Fix all issues with AI agents
In `@go.mod`:
- Around line 12-15: The go.mod upgrade to flow-go v0.45.0-internal-rc.3 changes
payload encoding (nil -> empty slice) and renames "scheduled callbacks" to
"transactions"; search for and update all code and tests that rely on nil vs
empty []byte semantics (e.g., functions/methods like MarshalPayload,
UnmarshalPayload, EncodePayload, ComputeHash, SignTransaction, VerifySignature,
PayloadEquals) to treat nil and []byte{} equivalently (normalize to empty slice
before encoding/hashing/comparison) and update any identifiers, comments, or
tests referencing "scheduled callbacks" to "transactions" (also update test
names such as payload_test, signing_test, equality_test to assert empty-slice
normalization and adjust expected literals accordingly).
In `@tests/go.mod`:
- Line 3: CI is using GO_VERSION: "1.25" while tests/go.mod declares go 1.25.1;
update the CI workflow to explicitly set GO_VERSION to "1.25.1" (where the
variable GO_VERSION or the setup-go version is defined) so the runner installs
Go 1.25.1 and matches tests/go.mod.
- Around line 8-13: The go.mod entry for modernc.org/libc (modernc.org/libc
v1.67.6) is not a verifiable published version—confirm whether this should be
the published v1.67.1 or if you intentionally need an unpublished fork; update
tests/go.mod to pin modernc.org/libc to the correct published tag (or document
and vendor the fork) and similarly review the pre-release flow-go entry
(github.com/onflow/flow-go v0.45.0-internal-rc.3...) along with atree,
golang.org/x/exp and other unlabeled deps referenced in tests/go.mod to ensure
tests account for FLIP-346 changes or commit-level breaking changes before
merging.
| github.com/onflow/atree v0.12.1 | ||
| github.com/onflow/cadence v1.9.7 | ||
| github.com/onflow/flow-go v0.45.0-internal-rc.3.0.20260129222115-cc0505f2afd5 | ||
| github.com/onflow/flow-go-sdk v1.9.13 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
find . -name "go.mod" -type f | head -5Repository: onflow/flow-evm-gateway
Length of output: 90
🏁 Script executed:
cat -n ./go.modRepository: 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:
- Bug fix: “Port v1.9.7-rc.1” (PR #4424)
- Other: dependency bump “Update to atree v0.12.1” (PR #4425)
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-go v0.45.0 (pre-release, Jan 29, 2026) calls out this breaking change in the release notes:
- [Breaking Change] Normalize nil payload value encoding to empty slice (
#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):
- Rename “scheduled callbacks” to “transactions” (
#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-sdk v1.9.13 does not list any breaking changes in its release notes. The release contains only a dependency bump:
- What’s changed: “Update to Cadence v1.9.7” (PR #989) and nothing else is called out. [1]
- The tag entry for v1.9.13 likewise indicates it’s just the Cadence update (merged PR #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)
- Adds a defensive check to prevent inserting a new element when an array already contains MaxUInt32 (~4.29B) elements, returning a user error instead. The notes mention that in practice such arrays would likely hit other client-enforced limits (e.g., Cadence / flow-go) before reaching that size. [1]
- Change delivered via PR
#624(ported fromonflow/atree-internal#17). [1] - Full changelog compare: v0.12.0…v0.12.1. [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]- The next release, v1.25.0 (2026-01-22), added SingleTenantHsm functionality (management API + resource types) plus related doc updates. [2]
- The earlier feature release, v1.23.0 (2025-09-11), added KEM-related enums and support for KEY_ENCAPSULATION and post-quantum/KEM algorithms (ML_KEM_768, ML_KEM_1024, KEM_XWING). [3]
If you need the exact v1.24.0 change list, it should be in the repo’s tag artifacts (typically kms/CHANGES.md for the kms/v1.24.0 tag) 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/crypto does 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:
- Tag:
v0.25.4 - Date: Jan 21, 2026
- Change (tag message): Merge PR Integration testing #38 — “Fix an issue with ‘bool’ type def in recent versions”
- Commit:
6848f9b(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:
- github.com/onflow/atree v0.12.1: Adds defensive MaxUInt32 check, no breaking changes
- github.com/onflow/cadence v1.9.7: No breaking changes (patch with atree update)
- github.com/onflow/flow-go-sdk v1.9.13: No breaking changes (updates cadence)
- github.com/onflow/crypto v0.25.4: Bug fix only, no breaking changes
Note: cloud.google.com/go/kms v1.24.0 changelog is not publicly documented; unable to verify for breaking changes.
🤖 Prompt for AI Agents
In `@go.mod` around lines 12 - 15, The go.mod upgrade to flow-go
v0.45.0-internal-rc.3 changes payload encoding (nil -> empty slice) and renames
"scheduled callbacks" to "transactions"; search for and update all code and
tests that rely on nil vs empty []byte semantics (e.g., functions/methods like
MarshalPayload, UnmarshalPayload, EncodePayload, ComputeHash, SignTransaction,
VerifySignature, PayloadEquals) to treat nil and []byte{} equivalently
(normalize to empty slice before encoding/hashing/comparison) and update any
identifiers, comments, or tests referencing "scheduled callbacks" to
"transactions" (also update test names such as payload_test, signing_test,
equality_test to assert empty-slice normalization and adjust expected literals
accordingly).
| module github.com/onflow/flow-evm-gateway/integration | ||
|
|
||
| go 1.25.0 | ||
| go 1.25.1 |
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:
Go 1.25.1 release availability and compatibility 2025 2026
💡 Result:
Go 1.25.1 (2025–2026): release availability + compatibility
Availability (when/where)
- Go 1.25.1 was released on September 3, 2025 as a minor revision to Go 1.25, with security fixes (notably in
net/http) plus bug fixes across several packages/tools. [1] - In 2026, Go 1.25 patch releases continued; for example, the Go project’s published version metadata shows go1.25.6 with a timestamp in January 2026 (meaning 1.25.1 is not the latest 1.25 patch in 2026). [4]
Compatibility (what it runs on / what changes to expect)
- Language/source compatibility: Go 1.25 maintains the “Go 1” compatibility promise, and “almost all Go programs” should continue to compile/run as before. [3]
- macOS: Go 1.25 requires macOS 12 (Monterey) or later (older macOS versions are unsupported). [2]
- Windows/ARM (32-bit): Go 1.25 is the last release that contains the broken
windows/arm(32-bit) port; it is removed in Go 1.26. [2] - Support window (important for 2026 planning): The Go project’s release policy states a major release is supported until there are two newer major releases (security/critical fixes land in supported releases via minor revisions). [1] Also, Go security fixes are prepared for the two most recent major releases. [5]
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:
golangci-lint Go 1.25 support compatibility
💡 Result:
golangci-lint’s Go-version compatibility is primarily determined by the Go version used to build the golangci-lint binary: it supports Go versions ≤ the build Go version, and new Go releases may additionally require internal/linter updates before they work well. [1][2]
Go 1.25 specifically
- The
golangci-lintproject tracked Go 1.25 enablement in “go1.25 support” (Issue#5873), and notes that sincev2.4.0,golangci-lintsupports Go 1.25 if the binary is compiled with Go 1.25; it also states their official release binaries are built with Go 1.25. [1] - If you install via a package manager (Homebrew/Nix/etc.) or
go install, you can end up with a binary compiled with an older Go version, which may break or fail on Go 1.25 projects; the docs recommend using official binaries rather than source builds for this reason. [1][3]
What to do
- Use an official
golangci-lintrelease binary (or Docker image) that is built with Go 1.25. [1] - Verify your binary: run
golangci-lint versionand confirm it says “built with go1.25.x”. [1] - If you must compile it yourself, compile with Go 1.25, and prefer
golangci-lint >= v2.4.0. [1]
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
[2] https://golangci-lint.run/docs/welcome/faq/
[3] https://golangci-lint.run/docs/welcome/install/local/
🌐 Web query:
GitHub Actions Go 1.25.1 runner support
💡 Result:
Yes—GitHub Actions can run Go 1.25.1, but you should install it via actions/setup-go rather than relying on what happens to be preinstalled on the runner.
- Go 1.25.1 exists (released 2025-09-03). [1]
- GitHub-hosted runner images only keep ~3 latest Go minor versions preinstalled, so the preinstalled 1.25.x (if present) is typically a newer patch than 1.25.1. [2]
actions/setup-gocan install an exact patch version (like1.25.1) by using the Go toolcache/manifest and falling back to downloading from the official Go distribution site if needed. [3]
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 GO_VERSION: "1.25", but tests/go.mod requires go 1.25.1. Update the CI configuration to explicitly use 1.25.1 to match the test environment requirement. golangci-lint v2.4 and GitHub Actions already support Go 1.25.1, so no toolchain compatibility issues exist.
🤖 Prompt for AI Agents
In `@tests/go.mod` at line 3, CI is using GO_VERSION: "1.25" while tests/go.mod
declares go 1.25.1; update the CI workflow to explicitly set GO_VERSION to
"1.25.1" (where the variable GO_VERSION or the setup-go version is defined) so
the runner installs Go 1.25.1 and matches tests/go.mod.
| 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-experimental-cadence-v1.8.7.0.20260109014156-2abea7b5732a | ||
| github.com/onflow/flow-go-sdk v1.9.10 | ||
| github.com/onflow/flow-go v0.45.0-internal-rc.3.0.20260129222115-cc0505f2afd5 | ||
| github.com/onflow/flow-go-sdk v1.9.13 |
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:
github.com/onflow/flow-emulator v1.16.3 release notes breaking changes
💡 Result:
I couldn’t find any v1.16.3 release/tag for github.com/onflow/flow-emulator. The Flow docs reference emulator releases in the v0.x series (for example, they link the emulator to v0.16.1 on the onflow/flow-emulator GitHub releases page), which strongly suggests flow-emulator is not versioned as v1.16.x. [1]
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., v0.16.3) or a different repo (e.g., flow-cli), tell me which and I’ll pull the exact breaking changes from the correct release notes.
Sources
[1] https://developers.flow.com/protocol/node-ops/node-operation/past-upgrades
🌐 Web query:
github.com/onflow/flow-go v0.45.0 release notes
💡 Result:
onflow/flow-go v0.45.0 (pre-release) — Jan 29, 2026: “Height Coordinated Upgrade on Mainnet28 at Block Height 140,478,444”. (newreleases.io)
What’s changed (high level)
- Bootstrapping / clusters: updated randomness used during bootstrapping; added cluster bootstrapping commands; added collection cluster bootstrapping + voting test. (newreleases.io)
- Scheduled transactions naming: “schedule callbacks” renamed to “transactions”. (newreleases.io)
- Network/versioning updates: updated Testnet system collection version; added “AN compatibility” for v0.44.0. (newreleases.io)
- Execution effort weights: updated per FLIP 346. (newreleases.io)
- Emulator / transient chains: added
MonotonicEmulatorto transient chains. (newreleases.io) - Storage / Access / Benchmarking: storage index execution result refactor; access sealed result index removal; access reindexing last block’s protocol data; benchmark manual cmd fix. (newreleases.io)
- Deployments: deploy LockedTokens and StakingCollection after scheduled transactions. (newreleases.io)
Full changelog compare range: v0.44.19...v0.45.0. (newreleases.io)
Citations:
- 1: https://newreleases.io/project/github/onflow/flow-go/release/v0.45.0?utm_source=openai
- 2: https://newreleases.io/project/github/onflow/flow-go/release/v0.45.0?utm_source=openai
- 3: https://newreleases.io/project/github/onflow/flow-go/release/v0.45.0?utm_source=openai
- 4: https://newreleases.io/project/github/onflow/flow-go/release/v0.45.0?utm_source=openai
- 5: https://newreleases.io/project/github/onflow/flow-go/release/v0.45.0?utm_source=openai
- 6: https://newreleases.io/project/github/onflow/flow-go/release/v0.45.0?utm_source=openai
- 7: https://newreleases.io/project/github/onflow/flow-go/release/v0.45.0?utm_source=openai
- 8: https://newreleases.io/project/github/onflow/flow-go/release/v0.45.0?utm_source=openai
- 9: https://newreleases.io/project/github/onflow/flow-go/release/v0.45.0?utm_source=openai
🌐 Web query:
github.com/onflow/flow-go-sdk v1.9.13 release notes breaking changes
💡 Result:
For github.com/onflow/flow-go-sdk v1.9.13 (released Jan 29, 2026), the published release notes list no breaking changes. The only change called out is:
- Update to Cadence v1.9.7 (PR
#989). [1]
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:
github.com/ncruces/go-strftime v1.0.0 release notes
💡 Result:
github.com/ncruces/go-strftime does not have GitHub “Releases”/release notes entries (the Releases page is empty), but it does have a v1.0.0 tag dated Oct 8, 2025, pointing at commit 7be8eef with the tag message “Document restrictions.” [1][2][3]
What changed in the v1.0.0 tag (commit 7be8eef):
- Documentation-only update: it documents format-string restrictions for
Parse,Layout, andUTS35. [3] Parse: documents specifiers not supported for parsing:%g %k %l %s %u %w %C %G %Q %U %V %W, and warns to avoid digits and the letter sequencesJan Mon MST PM pmin format literals. [3]Layout: documents specifiers not supported by Go time layouts:%f %g %k %l %s %u %w %C %G %L %N %Q %U %V %W, plus the same “avoid digits /Jan Mon MST PM pmin literals” restriction. [3]UTS35: documents specifiers not supported by UTS#35 conversion:%e %k %l %u %w %C %P %U %W. [3]
Note: The repo’s tags page shows v1.0.0 and v0.1.10 share the same commit (7be8eef) and date. [2]
References:
[1] https://github.com/ncruces/go-strftime/releases/tag/v1.0.0
[2] https://github.com/ncruces/go-strftime/tags
[3] ncruces/go-strftime@7be8eef
🌐 Web query:
github.com/onflow/atree v0.12.1 release notes
💡 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:
- v0.12.1 exists and is listed on pkg.go.dev, dated Jan 29, 2026. [1]
- The
test_utilspackage page for module version v0.12.1 is published Jan 29, 2026. [2] - The Cadence project updated its dependency to atree v0.12.1 (but does not include atree-specific release notes). [3]
How to see the actual changes: use GitHub’s tag comparison view for the atree repo (compare v0.12.0...v0.12.1) to get the commit/PR diff (since no release notes are published).
Sources
- [1] (pkg.go.dev)
- [2] (pkg.go.dev)
- [3] (newreleases.io)
Citations:
- 1: https://pkg.go.dev/github.com/onflow/atree/test_utils?tab=versions
- 2: https://pkg.go.dev/github.com/onflow/atree%40v0.12.1/test_utils
- 3: https://newreleases.io/project/github/onflow/cadence/release/v1.9.7?utm_source=openai
🌐 Web query:
golang.org/x/exp latest release notes
💡 Result:
golang.org/x/exp does not publish traditional “release notes” (it’s an experimental subrepo and typically ships as pseudo-versions rather than semver tags). The best equivalent is “what changed between pseudo-versions” via the repo log/diff.
- Latest published version (on pkg.go.dev):
v0.0.0-20260112195511-716be5621a96(published Jan 12, 2026) [1] - Previous version:
v0.0.0-20251113190631-e25ba8c21ef6(published Nov 13, 2025) [1] - The repo is hosted at
go.googlesource.com/exp/and you can use its commit log (or compare those two revisions) as the “release notes” view. [2]
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:
modernc.org sqlite v1.44.3 release notes
💡 Result:
modernc.org/sqlite v1.44.3 (released 2026-01-19) has a single changelog entry: “Resolves issue 243.” [1]
Issue #243 is titled: “darwin/arm64: checkptr panic in _unixModeBit when using race detector.” [2]
Sources: [1] [2]
🌐 Web query:
modernc.org libc v1.67.6 release notes
💡 Result:
I couldn’t find any upstream release notes (or even evidence of an existing tag) for modernc.org/libc v1.67.6 via publicly indexed sources.
What I can confirm from public registries is:
- The module’s upstream repository is
gitlab.com/cznic/libc. [2] - A public module index currently shows a latest published version around v1.67.1 (not v1.67.6). [1]
If you do have v1.67.6 in a go.mod, it may be:
- an internal/private tag not mirrored/indexed publicly, or
- a typo (e.g., you meant
v1.67.1), or - a version that exists upstream but isn’t reachable via the sources I can access.
To get authoritative “release notes” for exactly v1.67.6, the most reliable method is to compare git tags/commits in the upstream repo (gitlab.com/cznic/libc) and read the tag annotation / commit log for that version. [2]
Sources: [1], [2]
🌐 Web query:
github.com/onflow/flow-emulator releases versions available
💡 Result:
The onflow/flow-emulator versions available on GitHub are published as tags (and partially as “Releases”).
Most recent tags (newest → older):
- v1.16.3 (Jan 29, 2026)
- v1.16.2 (Jan 28, 2026)
- v1.16.1 (Jan 20, 2026)
- v1.16.0 (Jan 19, 2026)
- v1.15.3 (Jan 9, 2026)
- v1.15.2 (Jan 8, 2026)
- v1.15.1 (Jan 5, 2026)
- v1.15.0 (Dec 19, 2025)
- v1.14.0 (Dec 15, 2025)
- v1.13.2 (Dec 2, 2025) (github.com)
More older tags (examples):
- v1.13.1, v1.13.0, v1.12.3, v1.12.2, v1.12.1, v1.12.0, v1.11.0, v1.10.4, … (github.com)
For the full list, use the repository’s Tags page. (github.com)
Citations:
- 1: https://github.com/onflow/flow-emulator/tags
- 2: https://github.com/onflow/flow-emulator/tags?after=v1.13.2
- 3: https://github.com/onflow/flow-emulator/tags
🌐 Web query:
github.com/onflow/flow-emulator v0.16.3
💡 Result:
I couldn’t find any official release/tag v0.16.3 for onflow/flow-emulator via public references/search results; the Flow Developer Portal specifically points to flow-emulator release v0.16.1 (not v0.16.3). [1]
If you’re trying to confirm whether v0.16.3 exists, the most reliable check is to query the repo’s tags directly:
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:
[1] Flow “Past Network Upgrades” page referencing flow-emulator release v0.16.1 (and CLI distribution note).
[2] Flow Emulator docs noting it’s included with the Flow CLI.
🌐 Web query:
modernc.org libc v1.67.6 cznic
💡 Result:
modernc.org/libc is a Go module (a partial reimplementation of C’s libc in pure Go) whose upstream repository is GitLab: gitlab.com/cznic/libc (project by cznic). [1][2]
I could not find any public reference to a tag/release v1.67.6 for modernc.org/libc from the available indexes; the most recent version surfaced by package tracking is v1.67.1. [2]
If you’re trying to verify whether v1.67.6 exists in your environment, run:
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 modernc.org/libc v1.67.6 cannot be publicly verified—the latest published version is v1.67.1. Confirm whether this version is correct or should be v1.67.1.
Additionally, note that:
github.com/onflow/flow-go v0.45.0-internal-rc.3.0.20260129222115-cc0505f2afd5is a pre-release RC version with significant changes including execution effort weight updates per FLIP 346—ensure tests account for these.- Several versions (
atree v0.12.1,golang.org/x/exp,libc) lack published release notes; review changes via commit logs if breaking changes cannot be ruled out. flow-go-sdk v1.9.13has no reported breaking changes (only Cadence v1.9.7 update).
🤖 Prompt for AI Agents
In `@tests/go.mod` around lines 8 - 13, The go.mod entry for modernc.org/libc
(modernc.org/libc v1.67.6) is not a verifiable published version—confirm whether
this should be the published v1.67.1 or if you intentionally need an unpublished
fork; update tests/go.mod to pin modernc.org/libc to the correct published tag
(or document and vendor the fork) and similarly review the pre-release flow-go
entry (github.com/onflow/flow-go v0.45.0-internal-rc.3...) along with atree,
golang.org/x/exp and other unlabeled deps referenced in tests/go.mod to ensure
tests account for FLIP-346 changes or commit-level breaking changes before
merging.
2 participants
Description
Automatically update to:
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.