Releases
Develop → Releases lists the releases of the environment chosen in the header, newest first. The newest is live: what the players of that environment get.
Publish the draft
Section titled “Publish the draft”Publish the draft makes the next release of staging from the draft, with a note of what changes for players. Every row is checked again first; a publish with problems is refused with the list of them. The players of staging get the release at once.
Publishing an own module from the CLI makes a release
of staging too: the newest one with that module put in, and nothing else of the draft. Its From names the module and the version, such as
bonus 0.1.0-dev.3.
Promote
Section titled “Promote”Promote on a release of staging publishes the same release as the next version of production, with a note of its source. Production is never edited directly: it gets only releases you tested on staging.
A release that holds a dev build of a module is marked dev, and its Promote is disabled: publish that version as a release from the CLI and promote the release it makes.
Roll back
Section titled “Roll back”Roll back on an older release publishes its content again as a new version of that environment. The draft is not touched, so the fix you make next is still on top of the latest edits.
Who may
Section titled “Who may”The owner and editors publish, promote and roll back. Support reads.
What a release holds
Section titled “What a release holds”The installed module versions, the catalogs, the currencies and the day start of the project. The players and their data are not part of a release: a rollback never takes back a purchase.
A game client generated from a release keeps working with the next ones as long as the modules stay compatible, which the CLI checks when a module is built.