0.228.x✎

The daemon asks for a key, so other accounts on the computer cannot use it.

0.228.x2026-11-10

FeatureChangeBugfix

The daemon asks for a key, so other accounts on the computer cannot use it.

Releases

  1. 0.228.4A node map's paths stay inside the project.New2026-11-10
  2. 0.228.3A save cut off part-way leaves nothing behind, and Dynamic mode says when it cannot compile.New2026-11-10
  3. 0.228.2roswaal status and roswaal stop exit cleanly on Windows.New2026-11-10
  4. 0.228.1A link inside the project opens again on macOS and Linux.New2026-11-10
  5. 0.228.0The daemon asks for a key, so other accounts on the computer cannot use it.New2026-11-10

Warning

Worth knowing before you upgrade.
  • 0.228.4A map that synced a folder above the project stops compiling. Move the folder into the project. If your project needs one outside it, tell us.
  • 0.228.0Open the editor from the printed address. A tab left open while the daemon restarts asks for the new key: paste the new address into it. roswaal stop and roswaal status read the key from ~/.roswaal/daemon-<port>.token.

Added

  • 0.228.0A key for the daemon. roswaal serve makes a new key each time it starts and prints the editor's address with it. A tab opened from that address keeps the key for as long as it is open. Without the key, the daemon says only that it is running.

Changed

  • 0.228.0Getting started notes the path. A from-source install runs the first node on your path, so folders other accounts can write to belong off it.

Fixed

  • 0.228.4Map paths stay inside the project. A path, or the project file's output, that leads out of the project, such as ../shared or C:/Users/…, is an error in the map, shown as it is typed, and the project file is not written. It used to go into the project file without a word, pointing Rojo outside the project.
  • 0.228.4A Lune map's names cannot climb. A folder or file called .. or . is an error.
  • 0.228.3A cut-off save leaves nothing behind. A save that failed part-way could leave an empty <name>.<random>.tmp file beside the graph. It is removed now, and on the website a save writes straight to the file, which the browser keeps unchanged until the write is complete.
  • 0.228.3Dynamic mode says when it cannot compile. A graph it could not compile, such as one that no longer reads as a graph, was skipped without a word. The editor now names the file and the reason, once for each new problem.
  • 0.228.2Status and stop exit cleanly on Windows. With a daemon running, both did their work and then failed with exit code 127 and an assertion from Node. They exit with 0.
  • 0.228.2Status says when it was told nothing. For a daemon started by another account, or with no key for the port in ~/.roswaal, it says so instead of reporting no project open.
  • 0.228.1Links inside the project open. On macOS and Linux, 0.228.0 refused a file reached through a link that stays inside the project. It is followed as before; a link put in its place while it is being opened is still refused.
  • 0.228.0Delete keeps to what Roswaal made. It refuses .git, Packages, roswaal.json, the place backups and the output folder itself.
  • 0.228.0A folder holding only Packages or .git keeps them. A map folder moved into one is moved in beside them.
  • 0.228.0Files are checked again once open. A file swapped for a link between the check and the open is refused rather than read or written through.
  • 0.228.0Place and Rojo project paths stay in the project. A place or rojoProject in roswaal.json that leads outside the project is refused when the file is read.