Skip to content

Version numbering should start at v1 on first approved state, not on first save #73

Description

@tessak22

Problem

Quiver currently increments the version counter on every save, including pre-publish drafts. This means the first published version of an artifact can show as v2, v3, etc. depending on how many times it was edited before approval.

Expected behavior

Version numbering should only begin once an artifact reaches approved status. The first approved state should always be v1. Subsequent edits and republishes after approval would then increment to v2, v3, etc.

Why this matters

Versions are meaningful signals — they communicate how many times a piece of content has been intentionally updated and shipped. Pre-publish drafting is just iteration, not versioning. Conflating the two adds noise and makes version history harder to interpret.

Suggested approach

  • Track save history separately from version history
  • Only increment version counter on approved → save transitions
  • Display version number based on approved saves only

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions