Skip to content

upgrade sonic to v1.15.0 for go1.26 build - #37

Draft
isabst wants to merge 1 commit into
caidaoli:mainfrom
isabst:codex/upgrade-sonic-v1-15-0
Draft

upgrade sonic to v1.15.0 for go1.26 build#37
isabst wants to merge 1 commit into
caidaoli:mainfrom
isabst:codex/upgrade-sonic-v1-15-0

Conversation

@isabst

@isabst isabst commented Mar 18, 2026

Copy link
Copy Markdown

Summary

This change upgrades github.com/bytedance/sonic from v1.14.1 to v1.15.0 to restore build compatibility with Go 1.26.x. It also updates the indirect dependency github.com/bytedance/sonic/loader from v0.3.0 to v0.5.0 as part of the module upgrade.

Problem

Building the project with Go 1.26.1 failed with:

undefined: GoMapIterator in github.com/bytedance/sonic/internal/rt/stubs.go.

This prevented producing the kiro2api binary on modern Go toolchains.

Root Cause

sonic v1.14.1 includes Go-runtime compatibility code with build tags that do not cover Go 1.26, so the expected GoMapIterator type is not compiled for this toolchain. The project currently depends on that incompatible version.

Fix

Upgrade to sonic v1.15.0, which includes newer runtime compatibility updates for recent Go versions. No application code changes were required; only dependency metadata (go.mod / go.sum) changed.

Validation

After the upgrade, the project builds successfully with:

go build -o kiro2api main.go

on macOS arm64 with Go 1.26.1.

@isabst isabst changed the title [codex] upgrade sonic to v1.15.0 for go1.26 build upgrade sonic to v1.15.0 for go1.26 build Mar 18, 2026
vahnxu added a commit to vahnxu/kiro2api that referenced this pull request Apr 17, 2026
Go 1.26.x build fails with sonic v1.14.1 due to missing GoMapIterator
type. Upgrading to v1.15.0 restores build compatibility on modern Go
toolchains. Same fix as PR caidaoli#37 (isabst).

Verified with go 1.26.1 darwin/arm64 and linux/amd64.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant