a template starter repo for sveltekit projects
0

Configure Feed

Select the types of activity you want to include in your feed.

docs(process): add Releases section to AGENTS.md

- chronver for apps and templates, semver for packages
- release flow: bump-on-merge, bare chronver tag, --follow-tags
- downstream lineage via suede.from field in project package.json

+18
+18
AGENTS.md
··· 38 38 39 39 End-of-task skill: `.opencode/skills/task-lifecycle/SKILL.md`. The agent owns the task note — create it at task end without being asked, regardless of task size. Size of note scales with task. 40 40 41 + ## Releases 42 + 43 + Suede uses [chronver](https://chronver.org). Version lives in `package.json#version` (chronver format `YYYY.M.D[.N][-feature|-break]`; `pnpm version` normalizes leading zeros, so e.g. `2026.6.4`, not `2026.06.04`). 44 + 45 + ### Cutting a release 46 + 47 + 1. Final commit on the release branch, before merge, is `chore(release): cut <version>`. Bump with `pnpm version <version> --no-git-tag-version` (or hand-edit), commit only the `version` field. 48 + 2. Tag the merge commit on `main` with the bare chronver string, annotated. Push with `git push origin main --follow-tags`. 49 + 3. `git log <prev>..<new>` is the changelog. No `CHANGELOG.md`. 50 + 51 + ### Downstream lineage 52 + 53 + When a project duplicates suede, it adds `"suede": { "from": "<tag>" }` to its own `package.json` with the chronver tag of the suede commit it branched from. Suede's own `package.json` carries no such field. 54 + 55 + ### Version policy 56 + 57 + chronver for apps and templates (temporal releases, no API contract to break); semver for packages consumed by dependents (persistent breaking-change signals). 58 + 41 59 ## Guardrails 42 60 43 61 Always: