Skip to content

chore: bump sei-config to v0.0.25 - #501

Merged
bdchatham merged 1 commit into
mainfrom
chore/sei-config-v0.0.25
Jul 28, 2026
Merged

chore: bump sei-config to v0.0.25#501
bdchatham merged 1 commit into
mainfrom
chore/sei-config-v0.0.25

Conversation

@bdchatham

Copy link
Copy Markdown
Collaborator

Keeps the controller's sei-config pin in sync with seictl v0.0.70 (sei-protocol/seictl#242).

No behavior change. The controller consumes sei-config for mode strings, port constants and the ConfigIntent shape — never DefaultForMode. Config rendering happens in the seictl sidecar (sidecar/tasks/config_apply.go), which is why the sidecar image is the delivery vehicle for v0.0.25's seed cap and not this image.

Diff is the pin plus two go.sum lines. go mod verify clean, go vet clean, and the sei-config-consuming packages (internal/planner, internal/task, internal/platform) pass unchanged.

Context

v0.0.25 sets the seed profile's max_incoming_connection_attempts to 32 (concurrent connections per source IP) and carries sei-config#42's GigaExecutor baseDefaults change.

Worth knowing for anyone reading the rollout: TaskConfigApply runs on the init path only — update plans carry only p2pConfigPatch (planner.go:787-796; convention stated at planner.go:68-69 and :821). So a sidecar bump does not re-render config on running nodes. The seeds take the new default by being deleted and recreated.

Full T3 xreview: designs/seed-node-mode/xreview/sei-config-v0.0.25-rollout.md in bdchatham-designs (#130).

🤖 Generated with Claude Code

Keeps the controller's pin in sync with seictl v0.0.70. v0.0.25 sets the seed
profile's max_incoming_connection_attempts to 32 and carries the giga_executor
baseDefaults change.

No behavior change here: the controller consumes sei-config for mode strings, port
constants and the ConfigIntent shape, never DefaultForMode — config rendering
happens in the seictl sidecar (sidecar/tasks/config_apply.go). Planner, task and
platform tests pass unchanged.

Ledger: bdchatham-designs designs/seed-node-mode/xreview/sei-config-v0.0.25-rollout.md

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@cursor

cursor Bot commented Jul 28, 2026

Copy link
Copy Markdown

PR Summary

Low Risk
Lockfile-only dependency pin with no application code changes; operational impact depends on sidecar rollout, not this controller image.

Overview
Bumps the github.com/sei-protocol/sei-config module pin from v0.0.24 to v0.0.25, with matching go.sum checksum lines. No controller source changes.

This keeps the controller aligned with the newer sei-config release (seed max_incoming_connection_attempts default and related template defaults). The controller still only uses shared types/constants from sei-config; config rendering and the seed cap behavior land via the seictl sidecar image, not this bump alone.

Reviewed by Cursor Bugbot for commit 9a794b8. Bugbot is set up for automated code reviews on this repo. Configure here.

@bdchatham
bdchatham merged commit 3629b70 into main Jul 28, 2026
5 checks passed
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