Public releases

A release history people can trust.

Public release pages will come directly from approved release records, so the story cannot drift away from what actually shipped.

v0.15.2

Work names that make sense at a glance

Available now

Features, epics, stories, tasks, bugs, research, fixes, and checks now have labels that say what kind of work they are. Every relationship and earlier version remains connected behind the scenes.

Milestone: M038
Released: September 2026
Area: Project data
Proof: Build passed + production data verified

What changed

Work labels now describe the work.

Features, epics, stories, tasks, bugs, research, fixes, and checks are easy to identify
Forge assigns every label safely and prevents duplicates
Search, exports, releases, and connected tools use the new names

What remained stable

The complete history stayed connected.

Related work and the parent-child structure
Earlier versions, expected results, test proof, and decisions
Milestone scope, exact released code, and production results

Approved planM038Work and expected results

Exact codeVersion fixedThe released code is recorded

ChecksPipeline passedBuild and data checks attached

ResultProduction verifiedLive release confirmed

Planned

Permanent release links, searchable history, verified sources, privacy controls, and safe corrections.

Why this matters

Customers, teammates, and AI should answer “what changed?” from verified release information—not a hand-edited announcement.

Next · Evaluate

Decide where Forge fits.

Start with one product and one real release, then expand only if the result earns it.

Review the pilot →