Repository navigation
Closes #11. Also closes #8 — its fix has been on develop since PR #12 and reaches main here.
Why this release exists
v1.0.0 was not reachable from develop. main carried the release merge commit and develop
never got it back, so the branch under development had effectively never been released. 31 commits
had accumulated behind that.
What is in it
Almost entirely repair work. Three separate defects meant this API had never run end-to-end against
a working database, and four of its five quality gates were reporting success while checking
nothing.
| before | after | |
|---|---|---|
| schema loads on MySQL | no — aborted at the first table | 14 tables, container stays up |
| model attributes readable | no — all undefined |
yes |
| model associations registered | 0 | 4 |
| JWT revocation | never fired | fires |
pr-check.yml |
✅ regardless of outcome | blocking, + typecheck/build/audit |
security:semgrep |
exit 7, 0 rules | exit 0, 255 rules |
security:osv |
65 vulnerabilities | 0 |
security:audit |
exit 1 | exit 0 |
| tests | 0 | 25 |
Full detail in CHANGELOG.md.
Version choice
1.1.0, minor rather than major. The HTTP API surface is unchanged. The schema changes are
incompatible with an existing deployment — but there cannot be one, because the schema could not be
loaded by any MySQL until this release.
Verification on the release branch
Every gate the repo defines, run locally:
npm test 25 passed, 4 suites
npm run lint:ci 0
npm run typecheck 0
npm run build 0
npm run format:check 0
npm run knip 0
npm run markdownlint 0 errors
npm run dupes 0
npm run license:check 0
npm run security:semgrep 0 (255 rules)
npm run security:osv 0
npm run security:audit 0
npm run security:secrets no leaks
npm audit reports 0 vulnerabilities across the whole tree.
After merge
Per Git Flow: tag v1.1.0 on main, then merge main back into develop so the tag is reachable
and this drift does not recur — which is the root cause #11 actually names.