Deployments & versions

Keep each round of feedback tied to the prototype your team reviewed. Publish a new version when you want to share changes while keeping the previous round available.

Keep every review round

After installing the CLI, run artor publish without a named-link option to create a new, numbered version. Version 7 and version 8 have separate links and comments. A normal new publish leaves the previous version unchanged.

Publishing again to an existing named link can behave differently — see overwrite mode below.

Choose a version to review the feedback left on that round.

Aliases let you say “this is the current one”

An alias is a name for a link, such as latest or for-review:

• latest follows the newest published version automatically.
• A version number opens a specific version.
• A custom name lets you keep a link for a particular review or direction.

artor publish                    # create a new version; latest follows it
artor publish --alias for-review # publish to a named link; check overwrite mode below

For public links, choose Pinned for a specific version or Latest to follow new publishes. See Public sharing.

Republishing is fast

Artor reuses unchanged files when you publish again.

Get the source back

You can download a published version’s editable project files to continue working:

• artor pull keeps you linked to the same prototype. Your next publish adds to that project.
• artor remix creates a separate prototype you own, leaving the original alone.

Secret files are excluded from the saved source. See Remix & rename and publish size limits.

Honest limits

Overwrite mode is the default for named links. Only the prototype’s owner or an organization admin can replace a version this way. Organizations configured to create a new version for named publishes keep the previous content instead; contact Artor support if you need that setup.