docs(website): publish v0.18 blog post dated May 1

[ntucker]

Motivation

The v0.18 announcement post should reflect a May 1 publication date rather than April 24, matching the intended ship schedule.

Solution

Rename the blog file to use the 2026-05-01 date prefix so Docusaurus emits /blog/2026/05/01/v0.18-scalar-typed-downloads, update intra-post anchor links accordingly, and point the v0.18 migration skill at the same path.

Open questions

N/A

Made with Cursor

---

Note

Low Risk
Low risk documentation-only changes; main risk is broken internal links/embeds if any remaining references to the old blog date/path were missed.

Overview
Updates the v0.18 release blog post to publish under the May 1, 2026 URL, including updating all intra-post links/anchors and the migration skill doc link to point at the new /blog/2026/05/01/... path.

Tweaks the shared ScalarDemo embed to make row configurable (defaulting to false) and adjusts code-block collapse behavior, then updates the blog to render the demo with row={false}.

^{Reviewed by Cursor Bugbot for commit 464ee08. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs-site	Ready	Preview, Comment	May 1, 2026 0:18am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 464ee08

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR