15 lines
878 B
Markdown
15 lines
878 B
Markdown
# Repository Instructions
|
|
|
|
## Versioning and releases
|
|
|
|
- Treat `package.json` as the source of truth for the application version.
|
|
- Keep `package.json`, `build/package.player.json`, and `build/package.web.json` on the same version number.
|
|
- When the app version changes, update `CHANGELOG.md` in the same change.
|
|
- Keep database migration versions aligned with the release they actually belong to.
|
|
- If only part of a migration batch belongs to a newer release, split that batch into a separate migration entry instead of relabeling the earlier release.
|
|
- Do not bump migration versions just because the app version changed.
|
|
|
|
## Before finishing a versioned change
|
|
|
|
- Confirm the package version, changelog entry, and migration tags are consistent.
|
|
- If a release note mentions a feature or fix, make sure the matching code path or migration block is tagged to the same release. |