peter
f54dd98129
gate / frontend (push) Successful in 1m9s
gate / backend (push) Successful in 1m27s
A vitest that fails the gate when the newest release-notes entry's version diverges from the repo-root VERSION file (the two hand-edited version sources), plus a no-duplicate-versions check. Catches the "bumped one, forgot the other" release mistake.
22 lines
1.0 KiB
TypeScript
22 lines
1.0 KiB
TypeScript
import { readFileSync } from "node:fs";
|
|
|
|
import { describe, expect, it } from "vitest";
|
|
|
|
import { RELEASE_NOTES } from "./releaseNotes";
|
|
|
|
// DX-6: the app version is hand-maintained in two places that MUST agree — the repo-root VERSION file
|
|
// (the single source baked into the image + served at /api/version) and the newest RELEASE_NOTES entry
|
|
// (what the in-app "What's new" shows). A release that bumps one but forgets the other ships a wrong
|
|
// changelog or a mismatched banner. This locks them together so the gate catches the drift.
|
|
describe("release version consistency", () => {
|
|
it("RELEASE_NOTES[0].version matches the VERSION file", () => {
|
|
const version = readFileSync(new URL("../../../VERSION", import.meta.url), "utf-8").trim();
|
|
expect(RELEASE_NOTES[0]?.version).toBe(version);
|
|
});
|
|
|
|
it("release notes are ordered newest-first with unique versions", () => {
|
|
const versions = RELEASE_NOTES.map((r) => r.version);
|
|
expect(new Set(versions).size).toBe(versions.length); // no duplicate version entries
|
|
});
|
|
});
|