V2.2.0

[benjaminbellamy]

No description provided.

[andyne13]

Review

Checked the version bumps against the upstream release and the action bumps against the published action versions.

Verified correct

• The v2.2.0 tag exists upstream and was published 2026-09-03T16:24Z, so the card date "3 September 2026" is right and both retargeted links (hero badge, "Latest release") resolve.
• Chart 0.6.3, app version 2.2.0 matches infra/charts/openrag-stack/Chart.yaml at v2.2.0 exactly.
• The release-card bullets track the upstream changelog faithfully, including both breaking changes and their migration caveats.
• The CI bumps are sound: checkout@v5, configure-pages@v6 and upload-pages-artifact@v5 all exist and all run on node24, so the "off Node 20" goal is achieved. deploy-pages@v5 was already on main, and upload-pages-artifact@v5 pulls upload-artifact@v7, so the producer/consumer pair stays compatible. No breaking inputs affect this workflow.
• Markup checks out: grid-3, reveal-d2 and pill-red all exist in css/site.css, and the page parses with no tag-nesting errors.

1. Stale meta description — index.html:8

Every other version surface moved to 2.2, but the plain <meta name="description"> still ends AGPL-3.0, version 2.1 out now. That is the string search engines render in the result snippet, so the listing will advertise 2.1 while og:description, the JSON-LD softwareVersion and the hero all say 2.2.

2. sitemap.xml — lastmod still 2026-07-31

Already drifting before this PR, but a content release is the natural moment to bump it to 2026-09-03.

3. Link the migration docs from the two breaking-change bullets — index.html:1778,1782

The Milvus 3.0 bullet promises that "a migration package and documentation ship with the release" but gives no way to reach either. For a breaking change, the operator reading this card is exactly the person who needs one click rather than a hunt through the changelog. linagora.github.io/openrag/documentation/milvus_migration/ resolves, and .ticks li a is already styled, so links sit naturally in the card:

<li><b>Milvus 3.0</b> &mdash; the vector store moves to its next major version. Existing 2.x
deployments must be migrated before upgrading: download the
<a href="https://github.com/linagora/openrag/releases/download/v2.2.0/milvus_v3_migration.zip" rel="noopener">migration package</a>
and follow the
<a href="https://linagora.github.io/openrag/documentation/milvus_migration/" rel="noopener">migration documentation</a>.</li>

<li><b>Case-insensitive lexical search</b> &mdash; BM25 no longer distinguishes case. Existing
deployments need the accompanying
<a href="https://linagora.github.io/openrag/documentation/milvus_migration/#schema-migrations" rel="noopener">schema migration</a>.</li>

Use the release-asset URL github.com/linagora/openrag/releases/download/v2.2.0/milvus_v3_migration.zip — verified 200 and a valid zip. Don't copy the user-attachments URL from the release body; that form is a temporary upload link.

One deliberate detail: the asset URL should stay pinned to /download/v2.2.0/ rather than /releases/latest/download/. This bullet lives in a v2.2.0 release-notes card and should keep pointing at the v2.2.0 package permanently; latest would silently repoint it at 2.3's assets and break if the file is not carried forward.

4. Nit — index.html:1349

<span class="pill pill-red">Up</span>, while the other System status mock at index.html:921 uses pill-ok for the same "Up". pill-red is the brand/danger fill, so this mock reads as an alert. Pre-existing, just adjacent to a changed line.

5. Optional — omitted feature

The card covers five items; v2.2.0 also shipped indexing completion callback URLs (linagora/openrag#695), which is the kind of integration-facing API addition this site's "OpenAI-compatible API" audience cares about. Entirely reasonable to leave out for length — flagging the choice rather than the omission.

Nothing blocking beyond item 1.

[benjaminbellamy]

Thanks — all three actionable points are now fixed on the branch (d1af152, dbb1ab1, 7fe8a80).

1. Stale meta description — fixed. index.html:8 now ends AGPL-3.0, version 2.2 out now., so it lines up with og:description, the JSON-LD softwareVersion and the hero.

3. Migration links — done, using your snippets. Both bullets now link out: the Milvus 3.0 bullet to the pinned release asset releases/download/v2.2.0/milvus_v3_migration.zip and to the migration docs; the BM25 bullet to #schema-migrations. Agreed on keeping the asset URL pinned to v2.2.0 rather than latest — the card is a permanent record of that release. rel="noopener" with no target matches how the rest of the page treats LINAGORA-family links.

4. Nit — fixed. index.html:1348 now uses pill-ok, matching the equivalent mock at index.html:921.

2. sitemap lastmod — leaving it for now; it will get picked up separately.

5. Callback URLs — leaving the card at five bullets. It is already the longest of the three, and the two breaking changes plus the three headline features are what an operator needs from a release card. The full changelog link below the cards covers the rest.

[benjaminbellamy]

Follow-up on item 2: the sitemap is done after all, in 0be8c30. lastmod goes to 2026-09-04 rather than the release date — it describes when this page last changed, which is when this PR ships, not when v2.2.0 was published upstream.

That leaves only item 5 (callback URLs) deliberately not taken.

[andyne13]

All five review items are resolved. Verified at 0be8c30:

• Meta description now advertises 2.2, and no stale 2.1 / 2.1.1 reference remains anywhere in the page or the sitemap.
• sitemap.xml lastmod refreshed to 2026-09-04, and the file is well-formed.
• Migration links — the Milvus 3.0 and BM25 bullets now reach the package and the docs. The release asset and the documentation page both return 200, the #schema-migrations anchor genuinely exists on that page, and the asset URL is correctly pinned to /download/v2.2.0/ rather than latest, so the card keeps pointing at the 2.2.0 package after 2.3 ships.
• Console mock — both System status blocks now use pill-ok for "Up".
• The callback-URLs bullet was left out, which is a fair editorial call on card length.

index.html still parses with no tag-nesting errors. The CI bumps are unchanged from the earlier check: checkout@v5, configure-pages@v6 and upload-pages-artifact@v5 are all node24 and compatible with the deploy-pages@v5 already on main.

Content matches the upstream v2.2.0 release, and the chart line matches infra/charts/openrag-stack/Chart.yaml at that tag. LGTM.