Skip to content

fix(releases): correct the v2.2.0 spice-rs link and the v2.1.4 post date - #2146

Open
lukekim wants to merge 2 commits into
trunkfrom
fix/release-post-corrections
Open

fix(releases): correct the v2.2.0 spice-rs link and the v2.1.4 post date#2146
lukekim wants to merge 2 commits into
trunkfrom
fix/release-post-corrections

Conversation

@lukekim

@lukekim lukekim commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Two corrections to August release posts. Both are reproducible against public endpoints.

1. The v2.2.0 post links a spice-rs release that does not exist

The SDK Updates section links spice-rs v3.2.0. That tag was never published, so the link is a dead end for every reader who follows it:

$ curl -s -o /dev/null -w '%{http_code}\n' -L https://github.com/spiceai/spice-rs/releases/tag/v3.2.0
404

$ gh api repos/spiceai/spice-rs/tags --jq '.[].name' | head -4
v4.0.0
v3.1.0
v3.0.0
v2.0.0

$ gh api repos/spiceai/spice-rs/releases/latest --jq '.tag_name, .published_at'
v4.0.0
2026-08-25T...

v4.0.0 is the release that shipped with v2.2.0, and it carries exactly the features the post already lists — search, NSQL, async queries, query cancellation, and mTLS. The fix is the version number and the URL; the description is unchanged.

2. The v2.1.4 post contradicts itself on its date

The frontmatter says date: 2026-08-06. The title on the same post says Aug 5, 2026, and the v2.1.4 release was published on Aug 5:

$ gh api repos/spiceai/spiceai/releases/tags/v2.1.4 --jq '.published_at'
2026-08-05T19:15:42Z

Two independent signals say Aug 5 and one says Aug 6, so this changes the frontmatter to 2026-08-05. The frontmatter is what renders as the post date, so today the site shows a date that the post's own heading disagrees with.

The neighbouring posts are all self-consistent — v2.1.3 (2026-08-04 / "Aug 4"), v2.1.5 (2026-08-12 / "Aug 12") — which is why this one stands out.

If Aug 6 is deliberate and the title is what is wrong, say so and I will flip the change to the title instead.

@lukekim
lukekim requested a review from a team as a code owner September 1, 2026 22:06
@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

✅ Pull with Spice Passed

Passing checks:

  • ✅ Title meets minimum length requirement (10 characters)
  • ✅ Has at least one of the required labels: area/blog, area/docs, area/cookbook, dependencies
  • ✅ No banned labels detected
  • ✅ Has at least one assignee: lukekim

@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

🚀 deployed to https://0510efe3.spiceai-org-website.pages.dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants