chore(catalog): record the linked Spring Data store backfill (325 releases)

[amondnet]

Summary

This registers the 325 releases release.yml published for the five stores #717 added, 65 each, in catalog.json and markdown/<project>/<version>/:

Project	Versions
data-mongodb	4.2.0–5.1.1
data-neo4j	7.2.0–8.1.1
data-redis	3.2.0–4.1.1
data-relational	3.2.0–4.1.1
data-rest	4.2.0–5.1.1

With this and #716, the catalog covers every Spring Data store the release train documents through Antora.

It lands as one pull request instead of 325, for the same reason #350 and #716 did. The release workflow cuts every catalog branch from the default branch, so only the first automatic pull request could merge. Those 325 pull requests are closed and their branches deleted.

Provenance

Every page comes from a published archive, not a local rebuild. For each version the steps were:

1. gh release download.
2. shasum -a 256 -c against the published .sha256 asset.
3. Extract.
4. promote-markdown.ts.
5. update-catalog.ts --released-at <the release's publishedAt>.

The committed trees are therefore byte-identical to what consumers fetch.

bun run validate-catalog passes with 15 projects and 899 versions. The catalog.json diff only adds entries, apart from generated_at.

Notes

• All 325 release runs passed on their first attempt. Every release has its three assets, and every tag points at 3a5e8809, the default branch after feat(data): bound declared symlinks by the checkout and add the last five stores #717.
• One page is broken upstream: markdown/data-relational/3.2.9/value-expressions.md. It carries an "Unresolved include directive" line, because upstream's page includes 3.2.9@data-commons::page$value-expressions.adoc, which Commons 3.2.9 doesn't have. feat(data): bound declared symlinks by the checkout and add the last five stores #717 records this, and upstream removed the include in 3.2.10.

---

Summary by cubic

Backfills the catalog with 325 releases of five Spring Data stores — data-mongodb, data-neo4j, data-redis, data-relational, and data-rest — 65 versions each, from the release.yml runs that #717 added. This completes coverage of every Spring Data store the release train documents through Antora. The committed pages are byte-identical to the published release archives, verified against their .sha256 assets, and bun run validate-catalog passes with 15 projects and 899 versions. The PR lands as one pull request instead of 325 because the release workflow cuts all catalog branches from the default branch, so only the first automatic PR could merge; the other 324 PRs were closed and deleted. The catalog.json diff only adds entries and updates generated_at.

Known issue

• markdown/data-relational/3.2.9/value-expressions.md carries an "Unresolved include directive" because upstream includes a Commons 3.2.9 page that doesn't exist; the include was removed in 3.2.10.

^{Written for commit 54c5a7e. Summary will update on new commits.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[greptile-apps]

Confidence Score: 4/5

The PR appears safe to merge, though the advertised Data Relational 3.2.9 value-expressions page should be corrected.

Summary

Registers 325 published releases across five Spring Data stores and adds their converted Markdown trees.

• Catalog entries map each version to its release tag and publication time.
• One advertised Data Relational 3.2.9 page contains only an unresolved upstream include.

_{Reviews (1) · Last reviewed commit: "chore(catalog): record the linked Spring..."}