chore: release v0.0.27 (node freeze height) - #50
Merged
Conversation
Carries #49, which threads `freeze_height` through both schema layers, both legacy mapping directions, field metadata, and validation. The key is unreachable until it ships in a tagged version: sei-k8s-controller pins v0.0.22, which predates it, so a SeiNode setting freeze_height today has ApplyOverrides reject it as an unknown key. The key matters because seid reads `freeze-height` from app.toml to stop executing at a height while still serving query RPC, and the config file is the only route in. sei-k8s-controller builds a fixed `seid start --home <dataDir>` argv with no flag escape hatch, and carries no CRD field for freeze. So without this key there is no declarative way to stand up a frozen node at all. Unlike v0.0.26, the consuming seid build already exists. Freeze mode is on release/v6.6: the flag is registered in the vendored sei-cosmos (server/start.go), sei-tendermint refuses to freeze a validator, and sei-chain#4006 disables mempool traffic in freeze mode. This release closes the half of the path that was missing, rather than staging a knob ahead of its build. Consumed next by sei-sidecar, which resolves and validates overrides during config-apply and is therefore what makes this real on a running node, and then by sei-k8s-controller to keep its pin in sync. The controller needs no code or CRD change: it uses this library for types and constants, merges spec.overrides, and forwards the map verbatim. Releasing the key does not by itself change any node's behaviour. freeze_height defaults to 0, which means disabled, and validation rejects combining it with halt_height or halt_time. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
PR SummaryLow Risk Overview The tag marks a release that already includes Reviewed by Cursor Bugbot for commit 123664f. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Suggested version: Changes in (empty)
Automatically created GitHub ReleaseA draft GitHub Release has been created. |
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
1 participant
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.
Bumps
version.jsontov0.0.27. One line; no source change.What it carries
#49 (
fc2d1ef), which threadsfreeze_heightthrough both schema layers, bothlegacy mapping directions, field metadata, and validation.
The key is unreachable until it ships in a tagged version.
sei-k8s-controllerpins
v0.0.22, which predates it, so a SeiNode settingfreeze_heighttodayhas
ApplyOverridesreject it as an unknown key.Why the key matters
seidreadsfreeze-heightfromapp.tomlto stop executing at a height whilestill serving query RPC. The config file is the only route in:
sei-k8s-controllerbuilds a fixedseid start --home <dataDir>argv with noflag escape hatch, and carries no CRD field for freeze. Without this key there
is no declarative way to stand up a frozen node at all.
Different from v0.0.26: the consuming build already exists
The
accept-intervalrelease staged a knob ahead of its seid build. This onedoes not. Freeze mode is already on
release/v6.6:server/start.go),sei-tendermintrefuses to freeze a validator, forcing full-node mode,So this release closes the half of the delivery path that was missing.
Consumed next
sei-sidecarsei-k8s-controllerspec.overrides, and forwards the map verbatim — no code change, no CRD change.Behaviour
Releasing the key changes no node's behaviour on its own.
freeze_heightdefaults to 0, which means disabled. Validation rejects combining it with
halt_heightorhalt_time, matching seid's ownValidateFreeze.make testpasses on this branch.🤖 Generated with Claude Code