Publication history

Every time your project is published, Ryno keeps that version. The history is the list of those versions: you read who published each one, and when, and you read what changed from one to the next. It is a place to look, not a place to act.

Open the history

In the version footer of a project in the company catalogue, choose the history icon at the end of the line, View history. If your repository is already attached to your company, the same list is also reachable from its settings, under View publication history.

The list is grouped by day, newest first, and the version your team sees right now is marked as current.

Who publishes

A version comes from one of two places, and each row tells you which.

A publication by your pipeline happens when your default branch moves. Its row shows Pipeline where a name would be, with the date and the time.

A publication by a person happens when someone publishes the state of their open folder, without waiting for a merge. Its row shows that person’s name, with the date and the time.

A pipeline run that changed nothing does not add a version. The pipeline runs after every merge, so most runs would otherwise repeat the same version again and again, and the list would say nothing. You only see a new row when the shared part of the project is different from the one before it.

How long versions stay

Publications are kept for 365 days, then removed. On the Team plan, the history shows the last 90 days; on Business, the whole year. The top of the history says which of the two you are reading. When older publications are still kept but fall outside your plan, the end of the list says so and leads to the plans page of the web console; nothing is bought from the desktop app. The version your team sees now is the exception: it stays for as long as it is the current one, even if it is older than that. If you open a version that has been removed, Ryno says it is no longer available.

Read what changed

Choose a version to read what it changed compared with the one published just before it. The changes are gathered in three sections: Requests, Environments and Flows. Each change is one sentence, and each is marked as added, removed or changed in words, never by a colour alone.

To compare two versions that are not neighbours, choose a version, then Compare with… and pick the other one. Ryno reads the changes from the older to the newer, whichever order you clicked in.

Go back to an earlier version

Ryno does not restore a version. The history is there to read, and nothing in it rewrites what your team sees.

To go back, change your repository: revert the change you no longer want, then publish again from the repository. Your pipeline publishes the earlier state as a new version, and the history shows it like any other.