Public Release Notes Are Now Organized as Weekly Articles
VibeNest now has a cleaner release-notes pipeline. Instead of exposing a raw working changelog, we now publish user-facing release articles that group product changes by week and explain what changed in plain English.
Why This Changed
The internal changelog is useful while building: it captures implementation notes, deployment details, test counts, edge cases, and the small debugging stories that are easy to forget.
That is not the same thing users need on a website. Public release notes should be easier to scan, more consistent, and focused on what changed in the product experience.
What Is New
Release notes are now written as standalone Markdown articles with title, date, period, summary, and tags. Each post can be shown directly on the website without rewriting.
The first batch covers the current VibeNest history from mid-April through late May 2026, grouped into weekly or bi-weekly posts depending on shipping intensity.
How Future Updates Will Work
The working changelog stays lightweight. New raw entries go there while features ship. When a release cycle is ready, the full changelog is archived and the public version is rewritten as a clear release article.
Weekly posts are the default cadence. If a week is quiet, we can merge it into a bi-weekly update. If one major feature changes a core workflow, it can get its own article.
What Readers Should Expect
Future release notes will focus on outcomes: what users can now do, what became faster or safer, what was fixed, and what changed in important workflows.
We will keep enough technical context for builders to trust the details, but avoid dumping raw commits, migrations, and internal investigation notes into the public feed.
What This Enables
The changelog can now serve two audiences without compromising either one. Internally, it remains a detailed memory of what happened. Publicly, it becomes a readable product history that shows VibeNest is moving, improving, and taking reliability seriously.