Versions and updates

Only the latest release is served. How to see what changed and bring an update into a project.

Orvio serves each product's latest release. There is no way to ask for an older one.

What this means#

• A new release replaces the previous one in the catalog, the CLI and the MCP tools.
• If you name an old version, you get release_replaced and the latest version number.
• A cursor from an earlier release answers release_replaced; start the list again.
• Releases that were withdrawn disappear from every channel. Projects you already started with them stay licensed.

Check the current version#

$ orvio info sotto

Or ask: "Using Orvio, which version of Sotto is current?" Your tool uses get_product. The release block of every tool result also carries the version and the publication date.

Update a project#

Orvio never overwrites a file in your project. To bring in a new release:

1. 1

   Pull into a new folder

   TerminalCopy

   $ orvio pull sotto ./sotto-next
   

2. 2

   Compare

   Use your usual diff tool, or ask your agent to compare ./sotto with ./sotto-next and tell you what changed.

3. 3

   Merge what you want

   You decide which changes to take. Your own work is never touched.

Updates and the licence#

Updates are new releases and are only for active members. A project you started stays under the licence version it started under. A newer licence version applies only to files you take after it is published, and it can never reduce the rights of a started project.