Skip to content

chore(deps): bump sei-config v0.0.13 to v0.0.14#208

Merged
bdchatham merged 1 commit into
mainfrom
chore/bump-sei-config-to-v0.0.14
May 8, 2026
Merged

chore(deps): bump sei-config v0.0.13 to v0.0.14#208
bdchatham merged 1 commit into
mainfrom
chore/bump-sei-config-to-v0.0.14

Conversation

@bdchatham
Copy link
Copy Markdown
Collaborator

@bdchatham bdchatham commented May 8, 2026

Why

The controller validates the override map at intent-build time before forwarding to the sidecar (in internal/task/config_apply.go's validation step). Without sei-config v0.0.14 in the controller binary, BuildRegistry() doesn't know evm.enabled_legacy_sei_apis and the validation rejects:

validating config-apply: config-apply: invalid intent:
  [[ERROR] overrides.evm.enabled_legacy_sei_apis: unknown config field
   "evm.enabled_legacy_sei_apis"]

Reproduced today against harbor: every SeiNode child's config-apply task retry-loops on this error when the SND has spec.template.spec.overrides["evm.enabled_legacy_sei_apis"] set, which the orchestrator now does for legacy sei_* enablement.

The three-layer sei-config alignment

Component sei-config Status before Status now
Orchestrator's seictl CLI (v0.0.49) v0.0.14
Controller binary v0.0.13 v0.0.14 ✓
In-pod sidecar (post #204) v0.0.14

This PR closes the controller layer. Combined with the previously-merged #204 (DefaultSidecarImage bump) and #206 (revert of seLinuxChangePolicy), the override pipeline becomes fully aligned end-to-end.

go.sum churn

go mod tidy removed many transitive deps that sei-config v0.0.13 pulled in but v0.0.14 doesn't. Indirect dep cleanup, no functional change.

Tests

  • go test ./... green on the bump branch.

Test plan

  • CI builds new controller image
  • Bump platform's controller pin to the new image
  • Trigger nightly release-test; confirm config-apply task no longer rejects evm.enabled_legacy_sei_apis and sei_*-using tests run (LEGACY_SEI_REJECTIONS = 0)

Note

Low Risk
Low risk dependency-only change; primary impact is updating config-schema validation behavior via sei-config, with no controller logic changes.

Overview
Updates the controller’s sei-config dependency from v0.0.13 to v0.0.14 so intent-build/config-override validation recognizes newer config fields (e.g., evm.enabled_legacy_sei_apis).

Runs go mod tidy as part of the bump, dropping a large set of no-longer-needed transitive/indirect modules and keeping the existing genproto replace pin intact.

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

The controller validates the override map at intent-build time before
forwarding to the sidecar. Without sei-config v0.0.14 in the controller
binary, BuildRegistry() doesn't know evm.enabled_legacy_sei_apis and
the validation rejects:

  validating config-apply: config-apply: invalid intent:
  [[ERROR] overrides.evm.enabled_legacy_sei_apis: unknown config field
   "evm.enabled_legacy_sei_apis"]

The in-pod sidecar already had v0.0.14 (per #204's DefaultSidecarImage
bump). The controller is the third sei-config layer that needs the bump
for end-to-end override pipeline correctness.

Tests pass. The go.sum churn is a go mod tidy artifact — sei-config
v0.0.14 has a simpler transitive dep tree than v0.0.13.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@bdchatham bdchatham merged commit 56d90a4 into main May 8, 2026
3 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