Documentation

Product Versions

Plan releases and track progress with version milestones.

Versions let you group features into releases and track progress toward milestones. Manifest uses semantic versioning (e.g., 0.1.0, 0.2.0, 1.0.0) and organizes work into Next, Planned, and Backlog.

Next / Planned / Backlog

Manifest automatically categorizes your versions into three groups:

CategoryMeaning
NextThe first unreleased version, your current focus
PlannedAll other unreleased versions, queued for future releases
BacklogFeatures not assigned to any version (unscheduled work)

You can ask an agent to show you features by upcoming version:

Show me what's in the next few versions
0.2.0 (next)
├── ● OAuth Integration
└── ○ Rate Limiting

0.3.0 (planned)
└── ◇ Webhooks

Backlog
└── ◇ GraphQL API

Creating versions

You say:

Create version 0.2.0 for the auth release

Agent handles:

  • Creates the version milestone
  • Version becomes available for feature assignment

Version names must be semantic versions in MAJOR.MINOR.PATCH format (e.g., 0.2.0, 1.0.0). An optional v prefix is allowed (e.g., v0.2.0). Freeform names like "MVP" are not accepted.

Assigning features

You say:

Put OAuth in 0.2

Agent handles:

  • Assigns the feature to the version
  • Feature now contributes to version progress

How versions affect work order

Agents prioritize work based on versions:

  1. Next version first: Features in the next release get priority
  2. Priority within version: Lower priority number = higher importance
  3. Backlog last: Unassigned features after versioned work

This means when you ask "What should we work on next?", the agent pulls from the Next version before anything else.

Releasing a version

When all features in the Next version are implemented, the Web UI shows a banner prompting you to close and advance planning. You can also release a version through an agent:

Release 0.2.0

What happens on release:

  • Sets released_at timestamp on the version
  • Records a release history entry on the project
  • The next Planned version automatically becomes the new Next
  • New versions are auto-created to maintain at least 4 unreleased versions

Features can only be assigned to unreleased versions. Once a version is released, its feature assignments are locked.

Next step

Continue to Tools Reference.