Skip to content

feat(landing): the release badge comes from the newest release post - #13

Merged
vxnsin merged 1 commit into
mainfrom
hero-release
Nov 13, 2026
Merged

vxnsin merged 1 commit into
mainfrom
hero-release

Conversation

@vxnsin

@vxnsin vxnsin commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

The badge above the headline was written into hero.tsx and still said v0.9.0. Now a blog post can carry release: { version, badge } in its frontmatter, and the landing page shows the newest published post that has one, linking to it. A draft never shows. inkan-0-10 and inkan-0-9 carry it, so the badge reads v0.10.0 · MCP: every route a tool for AI clients and points to the 0.10 post. Checked in next dev; typecheck and lint clean.

A post's frontmatter can say release: { version, badge }; the landing page shows the newest
published one and links to it. 0.9 and 0.10 say so, so the badge reads v0.10.0 now.
@vercel

vercel Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
inkan-dev Ready Ready Preview Nov 13, 2026 9:03am UTC

@vxnsin
vxnsin merged commit 509409a into main Nov 13, 2026
3 checks passed
@vxnsin
vxnsin deleted the hero-release branch November 13, 2026 09:04

This branch was successfully deployed

1 active deployment
Preview — 84d9b0e1 Deployed Nov 13, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant