fix: resolve release calendar date at build time and add render tests

[Alex Iannicelli (atiannicelli)]

Pull Request

Summary

Stacked on #565 (feat/release-calendar-json), with suggested fixes for the three "should fix" items from the deep-dive review of that PR. Intended to be merged into the feature branch (or cherry-picked by John McCall (@lowlydba)) before #565 lands.

Refs #565, #525, OvertureMaps/ops-team#588

Changes

1. Resolve "today" at build time, not in the browser (docusaurus.config.js, src/releaseCalendar.js, src/components/ReleaseCalendar.jsx)

ReleaseCalendar.jsx called splitReleases(calendar.releases) at module scope, which defaulted today to new Date(). That runs once during SSR and again in the browser, so once a scheduled release date passes before the next deploy the client splits the rows differently from the server-rendered HTML and React warns on hydration. The config now computes buildDate once, uses it for the STAC fallback, and exposes it via customFields (same mechanism as releaseNoteDates). The component reads it through a useReleases() hook. splitReleases now requires today explicitly; the existing unit tests already passed it.

2. Add render tests for the new React code (vitest.config.mjs, src/__mocks__/*, src/components/__tests__/ReleaseCalendar.test.jsx, src/__tests__/codeBlock.test.jsx)

Follows the existing RTL pattern (SmartTable.test.jsx, CommunityTable.test.jsx) and the existing @docusaurus/useBaseUrl alias-to-mock approach. Adds aliases + mocks for @docusaurus/useDocusaurusContext (with setCustomFields() for tests), @docusaurus/Link, and @theme-original/CodeBlock. The calendar JSON is replaced with a small fixture via vi.mock so the tests exercise ordering, the shipped/upcoming boundary (including a release dated on buildDate), the * marker and footnote, TBD, release-notes links (shared by patch releases), and the pre-1.0 schema-link rule. The CodeBlock swizzle is renamed index.js → index.jsx so vitest can parse its JSX (Docusaurus resolves either extension); its tests cover placeholder replacement, non-string children pass-through, and prop forwarding.

3. Collapse ReleaseTable render props into one renderer (src/components/ReleaseCalendar.jsx)

releaseNotesPath() returns null for versions with no notes post and schemaLink(null) is null, so upcoming rows naturally render without links — one renderer serves both tables. This also removes the inconsistency where the history table wrapped TBD/schema in <code> and the schedule didn't. The "*reserved for quarterly major breaking change release" footnote now only renders when an upcoming row is actually marked majorChangeMonth.

Not included (left as "consider" items in the review): cwd-relative readdirSync('blog'), the majorChangeMonth: false entries in the JSON, and the duplicated JSON mention in release-calendar.mdx.

Testing

Command	Result
npm test (vitest run)	✅ 7 files passed, 1 skipped; 190 tests passed, 7 skipped (13 new)
npm run lint	✅ 0 errors (9 pre-existing warnings, none in changed files)
npx prettier --check <changed files>	✅ all pass (src/__mocks__/docusaurus-useBaseUrl.js already fails on the base branch; not touched)
npm run build	✅ [SUCCESS] Generated static files; build/release-calendar/index.html renders footnote, 3× TBD, 28 schema links, 28 notes links; __OVERTURE_RELEASE resolved to 2026-09-23.1 in all 5 example pages (wherobots, spark, sedona, pandas, ibis) with 0 unresolved placeholders

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Max errors	Warnings	Elapsed time
✅ JAVASCRIPT	eslint	38		0		0	13.14s
✅ MARKDOWN	markdownlint	286		0		0	0.3s
✅ SQL	sqlfluff	79		0		0	3.91s

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@10.1.0 --custom-flavor-setup --custom-flavor-linters JAVASCRIPT_ES,MARKDOWN_MARKDOWNLINT,SQL_SQLFLUFF

Show us your support by starring ⭐ the repository

[Alex Iannicelli (atiannicelli)]

bad A.I.