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
Open
fix(releases): correct the v2.2.0 spice-rs link and the v2.1.4 post date#2146lukekim wants to merge 2 commits into
lukekim wants to merge 2 commits into
Conversation
Contributor
✅ Pull with Spice PassedPassing checks:
|
Contributor
|
🚀 deployed to https://0510efe3.spiceai-org-website.pages.dev |
ewgenius
approved these changes
Sep 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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: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 saysAug 5, 2026, and the v2.1.4 release was published on Aug 5: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.