Overview
CHANGELOG.md is 32,717 bytes — larger than any source file in the repository — and is tracked only through a .gitignore force-add. package.json is at 1.15.0 while app.json says 1.0.0, so it is unclear which versions the changelog entries correspond to. There are no git tags visible in the recent history and no release workflow linkage, so an entry cannot be traced to a commit range or a store submission.
Specifications
Features:
- Entries anchored to git tags and release dates
- A documented release process linking
release.yml, git tags and changelog entries
- Older entries archived so the working file stays readable
Tasks:
- Reconcile changelog entries against the real version history
- Tag releases in git and link each changelog heading to its comparison range
- Have
.github/workflows/release.yml verify a changelog entry exists for the version being released
- Archive pre-1.0 entries to
docs/CHANGELOG-archive.md
Impacted Files:
CHANGELOG.md
.github/workflows/release.yml
package.json
app.json
Acceptance Criteria
- Each changelog version maps to a git tag
- A release without a changelog entry fails
- The working changelog is a readable size
Overview
CHANGELOG.mdis 32,717 bytes — larger than any source file in the repository — and is tracked only through a.gitignoreforce-add.package.jsonis at 1.15.0 whileapp.jsonsays 1.0.0, so it is unclear which versions the changelog entries correspond to. There are no git tags visible in the recent history and no release workflow linkage, so an entry cannot be traced to a commit range or a store submission.Specifications
Features:
release.yml, git tags and changelog entriesTasks:
.github/workflows/release.ymlverify a changelog entry exists for the version being releaseddocs/CHANGELOG-archive.mdImpacted Files:
CHANGELOG.md.github/workflows/release.ymlpackage.jsonapp.jsonAcceptance Criteria