v0.4.62

Development agreement and privacy previews now use short notices stating that DevGrail is not live yet.

Agreements, accepted once and kept current. Someone who has to accept sees a short "Before you start" step for each agreement (an administrator the Operator Agreement and then the User Agreement, anyone else the User Agreement) and then continues where they were going. When an agreement changes, one banner gives the date to accept it by, 30 days after the new version arrives; a wording fix asks nobody. Until then dashboard, API, MCP and new terminal access wait; running workloads continue and your files can still be exported. Agreements & privacy lists each document with where you stand on it, and installation reporting is now on Administration. There is no setting to turn acceptance off.

Every installation sends a daily heartbeat, and says exactly what is in it. Once an administrator accepts the Operator Agreement, DevGrail sends that acceptance and a heartbeat to the site it was installed from, at each start and then daily: random IDs, a sequence number, the release, the operating system and the CPU architecture, and nothing about users, workspaces or usage. It cannot be turned off. The installer, the Operator Agreement step and the Agreements & privacy page, which every user can open, list each field, and Administration shows the last heartbeat exactly as it was sent. If the installation's identity cannot be opened (a config.yaml that does not belong to the database, or a damaged instance file), only the heartbeat stops: Administration says why, and everything else keeps working. When reporting needs an administrator (that, or the DevGrail site refusing this installation's credential), Administration explains what happened and every administrator gets a notification when it starts and when it ends. When the identity cannot be recovered (the site has revoked or rejected its credential, or the config that can read it is lost), an administrator can start a new installation identity there, with their password and by accepting the Operator Agreement again for it.

The server downloads its legal documents itself. Releases no longer carry them. The installer links the three documents, says that installing, unattended included, does not accept them, and waits up to two minutes for the server to have them. If it cannot get them, the install ends with an error, and DevGrail keeps running and trying.

IPv6 visitors are seen as themselves. On a server with IPv6, DevGrail now serves IPv6 visitors directly, so a route's IP addresses can name them, Add my IP adds a browser's own IPv6 address, and the sign-in lockout counts each IPv6 visitor separately instead of all of them together. Before, every IPv6 visitor reached DevGrail from one internal address, so none could be named and one could lock the others out. The installer turns this on when the server has a public IPv6 address and route, and decides again on every run; --ipv6=no keeps it off. Add AAAA records for your domain and the wildcard pointing at the server's IPv6 address: the installer prints them, and warns about an AAAA record that points somewhere else, since Let's Encrypt would use it. Workspaces stay IPv4-only.

The installer needs Docker Engine 28.0 and Docker Compose 2.33.1 or newer. A server with an older Docker is stopped before anything changes, with the versions it found. A server without Docker still gets the current one installed.