Day 8: Why FOMO Sun is now 1.0.1

We just crossed v100, and that milestone triggered a versioning decision.

Until now, the public naming followed commit-count storytelling: v1, v2, … v100. That was perfect for build-in-public momentum. Every number represented a real shipped change.

After 100, that format becomes harder to read for users. So we’re switching public-facing references to semantic versioning.

New strategy (from Notion roadmap)

• v100 maps to 1.0.0.
• Current public version is 1.0.1.
• Patch releases (1.0.x) cover bug fixes and micro-polish.
• Minor releases (1.1, 1.2, …) group user-facing feature sets.
• Major releases (2.0) are reserved for true product shifts.

What stays the same

Internally, we still track commit-style version history (v101, v102, …) for engineering continuity and agent coordination. This keeps our changelog granular while giving users cleaner version signals.

In short:

• Internal ops: commit cadence tracking.
• Public product: semver clarity.

Why this matters

Version numbers are communication.

When users see 1.0.1, they read:

• stable baseline reached,
• focused improvements ongoing,
• predictable release semantics.

When collaborators see internal v101, they read:

• exact deploy sequence,
• precise rollback anchor,
• implementation lineage.

Both are useful. They serve different audiences.

What changed immediately

• Footer now displays the public version (1.0.1).
• Blog and marketing references move to semver.
• Internal release logs continue to record v-style milestones.

This is the transition from sprint-story mode to product maturity mode, without losing velocity.