Repository navigation
docs(cli): document os migrate + dev autoMigrate self-heal (#2186 follow-up) - #2205
Merged
Merged
Conversation
…ollow-up) Follow-up to #2196 — the schema-drift / `os migrate` feature shipped with no docs. - cli.mdx: new "Schema migrations" section — `os migrate plan/apply`, the safe/needs-confirm/destructive categories, `--allow-destructive`, and the dev-only `autoMigrate:'safe'` self-heal (force-disabled in production). - objectstack-platform SKILL: add `os migrate plan/apply` to the CLI cheat sheet. - objectstack-data SKILL: "Schema evolution on an existing database" — the sync is additive-only; relaxing `required` / type changes / drops on a live DB need `os migrate` (dev auto-heals loosening). Names the tell-tale: `/meta` says optional but a write 400s "<field> is required" = stale NOT NULL, not a validator bug. Body-only skill edits (frontmatter unchanged → generated skill docs don't drift). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Follow-up to #2196 (#2186) — the schema-drift /
os migratefeature shipped with no documentation. This adds it.content/docs/getting-started/cli.mdx— new Schema migrations section:os migrate plan/os migrate apply, the safe / needs-confirm / destructive categories,--allow-destructive, and the dev-onlyautoMigrate:'safe'self-heal (force-disabled in production; SQLite reconciles via data-preserving table rebuild).skills/objectstack-platform/SKILL.md—os migrate plan/applyadded to the CLI cheat sheet (the ops/migrations skill).skills/objectstack-data/SKILL.md— new Schema evolution on an existing database note: the sync is additive-only, so relaxingrequired/ type changes / drops on a live DB needos migrate(dev auto-heals loosening). Calls out the tell-tale —/metareports a field optional but a write still 400s"<field> is required"= a staleNOT NULLcolumn (physical drift), not a validator bug.Docs/skills only — no versioned package touched (hence
skip-changeset). Skill edits are body-only, so the frontmatter-generated skill docs don't drift.🤖 Generated with Claude Code