chore(deps): bump sei-config v0.0.13 to v0.0.14#208
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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). Withoutsei-config v0.0.14in the controller binary,BuildRegistry()doesn't knowevm.enabled_legacy_sei_apisand the validation rejects:Reproduced today against harbor: every SeiNode child's
config-applytask retry-loops on this error when the SND hasspec.template.spec.overrides["evm.enabled_legacy_sei_apis"]set, which the orchestrator now does for legacysei_*enablement.The three-layer sei-config alignment
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 tidyremoved many transitive deps thatsei-config v0.0.13pulled in butv0.0.14doesn't. Indirect dep cleanup, no functional change.Tests
go test ./...green on the bump branch.Test plan
config-applytask no longer rejectsevm.enabled_legacy_sei_apisand 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-configdependency fromv0.0.13tov0.0.14so intent-build/config-override validation recognizes newer config fields (e.g.,evm.enabled_legacy_sei_apis).Runs
go mod tidyas part of the bump, dropping a large set of no-longer-needed transitive/indirect modules and keeping the existinggenprotoreplace pin intact.Reviewed by Cursor Bugbot for commit 0a6e066. Bugbot is set up for automated code reviews on this repo. Configure here.