Keeping a project current
Yosr Seed generates a project once. You own the tree from the first commit. yosr-seed upgrade reports what changed since create; it writes nothing and does not apply updates.
What create records
Choices live under .seed/, especially .seed/answers.json (template id, version, options, style snapshot). That record helps you and your agents remember what was chosen. It does not apply newer template files by itself. A project from create is recorded as created; a project from adopt is recorded as adopted.
Upgrade reports; it does not apply
yosr-seed upgrade reads .seed/answers.json and reports the template you created with, the latest published CLI (when the registry is reachable), official migration notes, and which recorded files still match, you changed, or now differ upstream. It exits 0 when the report succeeds. It never writes to your tree, never merges files, and never offers a later create-time option (for example a later database choice or --ci) as an upgrade of an old project.
Adopt adds a rulebook, not an app rewrite
yosr-seed adopt is for an existing repo you already own. You name a Yosr Seed template. It always previews first (including whether gate would pass today), then may add AGENTS.md and pointer files plus a .seed/ record marked as adopted. It does not rewrite application code, and yosr-seed upgrade refuses adopted projects.
Gate does not upgrade
yosr-seed gate (with a pinned CLI version in CI, or a local install) re-runs the template’s checks on the current project tree. It does not pull a newer scaffold, rewrite options, or migrate dependencies.
Opt-in CI recipe (not an upgrade)
At create, you can opt in to a sample GitHub Actions workflow that runs the same yosr-seed gate as locally, with the CLI version pinned (never @latest). That is a CI recipe for the generated project. It is not an upgrade or migrate command, and it does not change your app when Yosr Seed ships a new cut. On Next.js, --ci replaces the template-local ci.yml so only the pinned gate workflow remains (plain gate does not run Playwright e2e; use gate --e2e).
Dependency updates vs template changes
- Dependency updates — use your package manager (
pnpm,npm, oruv) and review the lockfile. You control when libraries move. - Template changes — when Yosr Seed ships a new cut, read Releases and port what you need by hand. There is no file-by-file migration guarantee.
- New scaffolding choices — options such as Vite + React, Astro, or Hono MongoDB apply to new
createruns. They are not applied automatically to older projects.
Manual notes: 0.1.x → 0.2.x
Hono and FastAPI — CORS_ORIGINS
0.2.0 added CORS so a browser front end (for example Vite + React on port 5173) can call the API. If your project was created before that:
- Add
CORS_ORIGINSto.env/.env.exampleas a comma-separated list of allowed origins. A useful local default ishttp://localhost:5173,http://127.0.0.1:5173. - Ensure the app wires CORS middleware from settings (Hono and FastAPI templates do this in current scaffolds). If your older tree lacks that middleware, copy the pattern from a fresh create of the same template version you want to match.
- Point the SPA’s
VITE_API_URLat the API. CORS alone does not configure the client.
Other useful ports
- Hono MongoDB, Vite + React, and Astro are new create options, not patches onto an existing Next.js or API tree.
- Re-read generated README sections after comparing with a fresh project if you adopt Docker Compose or auth overlays by hand.
Practical loop
- Update dependencies when you choose to.
- Skim Releases when you care about scaffold changes.
- Port only what you need into your tree.
- Run
yosr-seed gateto verify the project you have.