You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(migrate,objectql): the upgrade path names the data migrations still open here (#3438) (#4253)
Both value-shape gates fail toward leniency — a deployment that never runs its
migration keeps warning instead of rejecting, and keeps every released file
forever. That default is right and completely silent, so a gate could sit open
for the life of a deployment without anyone learning one command ends it.
Two announcements, each where an upgrade actually looks:
- `os migrate meta --from 16` ends by naming the data migrations a chain
crossing into 17 leaves behind, scoped to the field classes the author's own
metadata declares; --json carries the same list as `dataMigrations`. The
command reads no database, so it reports what remains to do and never claims
what a deployment has done — which is why the ADR's "with their gate status"
lands on the other half.
- The server logs one line per open gate at boot, naming the command that
closes it. Only the lax posture announces itself; a verified gate already
logs that it enforces, and an app declaring neither class costs nothing and
says nothing.
On `kernel:bootstrapped`, not `kernel:ready`: the answer depends on the storage
service's own ready handler, which registers sys_migration and may attest a
store it just created — racing it would tell a brand-new deployment its gates
are open moments after they closed.
Enforcement is unchanged: same gates, same flags, same default.
Claude-Session: https://claude.ai/code/session_01KM46HedAWLbkuZyMBXn5wJ
Co-authored-by: Claude <noreply@anthropic.com>
0 commit comments