Skip to content

The Lovable Feature AtlasIndependent community catalog

Atlas
Workflow

Versioning 2.0

GAWorkflowReleased Mar 2025All plansSource: lovable.dev

Versioning 2.0 is Lovable's Workflow feature: Improved history, restore points, and version tracking.

Versioning 2.0 brings better history, named restore points, and clearer tracking across iterations so you can move fast without losing work.

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

  1. Stand it up from scratch

    You have read the record and want Versioning 2.0 working in a real project rather than a sandbox.

    Set up Versioning 2.0 in this project — improved history, restore points, and version tracking. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

    Expected outcome

    A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

  2. Recover from bad edits

    The record lists this as one of the jobs Versioning 2.0 is meant for, so it is a fair first test of whether it fits your app.

    In this project, use Versioning 2.0 for recover from bad edits. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

    Expected outcome

    One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

  3. Review it before you publish

    Versioning 2.0 is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

    Review how this project uses Versioning 2.0 before I publish. Check restore points and inline diff history, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

    Expected outcome

    A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

  4. Compare iterations

    A second job the record lists for Versioning 2.0, useful once the first path works.

    Extend this project so Versioning 2.0 also covers compare iterations. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

    Expected outcome

    A second path built on the same setup, plus a note on what was shared and what was added.

Capabilities

  • Restore points
  • Inline diff history
  • Stable rollback

Use cases

  • Recover from bad edits
  • Compare iterations

The link to lovable.dev uses a referral code. The atlas is otherwise unsponsored.

Frequently asked

  • What is Versioning 2.0?

    Versioning 2.0 is Lovable's Workflow feature: Improved history, restore points, and version tracking. Versioning 2.0 brings better history, named restore points, and clearer tracking across iterations so you can move fast without losing work.

  • Is Versioning 2.0 GA or in beta?

    Versioning 2.0 is generally available (GA) on Lovable.

  • What Lovable plan includes Versioning 2.0?

    Versioning 2.0 is available on all Lovable plans.

  • When did Versioning 2.0 launch?

    Versioning 2.0 launched on Mar 3, 2025.

Related in Workflow

See all →
Post on XLinkedIn

What Lovable Shipped

One email a week. Every new feature. Nothing else.

A curated Monday roundup of every Lovable feature added or promoted to GA in the past week — pulled straight from the atlas.

No spam. Unsubscribe anytime. Independent, not affiliated with Lovable AB.