Canonical update flow
BUMP IT
BUMP IT is the release move that keeps one app identity alive while the underlying artifact changes. It is how Vibecodr avoids turning every update into a new listing.
Release model for shipping the next version on the same canonical public app.
Implementation focus
Use this model whenever you want to update a live app, preserve backlinks and embeds, and keep older cuts exact for rollback or pinned references.
Expected outcomes
- Advance the live Drop without fragmenting the public app identity.
- Keep exact cuts available for rollback, embeds, and documentation references.
- Know when to publish as a new app instead of updating the existing one.
Canonical update flow
BUMP IT moves the live Drop for an existing app to a newer artifact while preserving the public app identity. It is the mechanism that lets a project evolve without losing backlinks, embeds, comments, remixes, or discovery continuity.
Older cuts remain exact references. The live route advances, but pinned or historical references can still point at the specific artifact they were created for.
- Use BUMP IT when the viewer should understand the release as the same app, improved.
- Publish a new app when the concept, audience, or public identity should split.
- Keep release notes and metadata aligned with what changed for viewers.
Rollback and reference behavior
The update model depends on immutable artifacts. Because each cut is preserved, the platform can reason about rollback, exact embeds, and historical references without pretending the old code was rewritten.
This is why publication is stricter than local preview: a public release becomes part of the app's lineage and social graph.
- The current Drop is the live app pointer.
- Artifacts are exact release records.
- Embeds and docs can choose live behavior or exact-cut behavior depending on the contract.
Example and read next
Example: you fixed a bug in an existing public app and want embeds, backlinks, comments, and discovery history to stay attached. Use BUMP IT so the live Drop advances without fragmenting the app identity.
Use these related pages when you need the next layer of guidance. They point to the most likely follow-up tasks, not every page that happens to touch the same system.
- Read next: Source & Versions (/docs/source)
- Read next: Studio (/docs/studio)
- Read next: VibeComposer (/docs/composer)
- Read next: How-To Guides (/docs/how-to)