Upgrade DIN
An upgrade is a new install over the old one: stop the field, run the new release's installer, and check the result. Your records, your token and your settings are kept.
Why stop the field first
From 1.0.30 the installer stops a field from the same install that is still running before it replaces the programs, then starts the new one (unless you pass --no-start). Installers before 1.0.30 did not: with those, the old field kept serving and din field start reported it was already up. Stopping it yourself first is harmless with any release, so the steps below keep it.
Steps
1. See what you run now:
din version
2. Stop the field. If you have din console running in a terminal, stop that too (Ctrl-C in its terminal).
din field stop
3. Download and verify the new release, unpack it, and run its installer with the same options you used the first time (for example the same --prefix or --port):
tar xzf din-<version>-linux-x86_64.tar.gz && cd din-<version>
sh install.sh
The installer starts the field again when it finishes. If you install with --no-start, start it yourself:
din field start
4. Check it:
din version
din status
What is kept
~/din/records: your records. The installer never deletes or rewrites them.~/din/.din/field.token: an existing token is never overwritten, so your field opens with the same token.~/din/.din/field.env: an existing settings file is left alone. To pick up a new default, delete it and install again.~/.din/plugin.env: the plugin's settings, left alone if present.~/din/.din/license.keyand the entitlement filesdin activatewrote: the installer does not touch them.- The login entry
din autostart onmade, if you turned it on. It runs~/din/bin/din, so from the next login it runs the new release. ~/din/.din/hosted.env, if you randin hosted connect.~/din/fields/: every field you made withdin field new, each with its own records, token and settings, and the list of them in~/din/.din/fields.json. The routes in~/.din/routes.jsonare kept too.~/din/bin/webhooks.json, the webhook subscriptionsdin webhooksand the console write: the installer replaces the programs one by one and leaves it in place.~/.din/capture-map.json, the project foldersdin capturereads, and~/.din/vault, the originalsdin import claude-aikeeps: the installer never opens either.
What is replaced
- The fifteen programs in
~/din/bin(1.0.39 addsdin-libcatalog, the library catalog clientdin deps refreshruns, anddin-regrade, the driverdin regrade --runruns; 1.0.40 addsdin-source, which writes the redacted views of the sources your records cite, anddin-referee, the review funnel:din-referee --planforecasts the judge pass for free, and the judge pass runs on your own inference at your plan's reading level; 1.0.41 addsdin-grade, the grader:din-importhands it every grading command), and thedin-recalllink. - The plugin payload in
~/din/plugin. The plugin's installer runs again for the agent you pick (Claude Code, Cursor, OpenCode, Codex or Gemini CLI; see Install).
From 1.0.41 to 1.0.42
1.0.42 is this release. The steps above are the whole upgrade. Your records, token, settings, fields, routes and licence are kept. What is new:
1. din update moves an install to a new release from now on. It checks the release's signature itself, keeps the version it replaces, and din update --rollback puts it back; your stores and records are never rolled back. The first move off 1.0.41 is the one-line installer or install.sh, since 1.0.41 has no din update. 2. Fields you run from your own units can be handed to DIN. din field adopt <unit> takes over a hand-made unit, launcher or systemd template (din-field@.service and every instance) and keeps the original beside it. After that, din update --restart restarts every field it manages on the new programs. 3. An install in a new folder keeps your licence when it holds on this box, or says loudly that it is unlicensed and gives the din activate line.
From 1.0.40 to 1.0.41
1.0.41 was the release before this one. The steps above are the whole upgrade. Your records, token, settings, fields, routes and licence are kept. What is new:
1. Grading is its own program, din-grade. The installer puts it in ~/din/bin beside din-import, which reads, redacts and places your records and hands every grading command to din-grade. Nothing to do: din grade and din import work as before. A download without din-grade is refused by the installer. 2. din-referee --plan needs no options on a plain install. It finds the field's store from the install's field.env too (its FIELD_STORE= line, the install found as din finds it: DIN_PREFIX, else ~/din), and reads the field token from the same file (its FIELD_TOKEN_FILE= line), so neither --store nor --token-file is needed there. The token file must be private (0600).
From 1.0.39 to 1.0.40
1.0.40 was the release before this one. The steps above are the whole upgrade. Your records, token, settings, fields, routes and licence are kept. Two things to check:
1. A field setting you export in your shell goes in field.env. A field that din starts (din field start, din console, din autostart on, or a session hook waking it) now takes its settings only from ~/din/.din/field.env, never from the shell or the repository it was started from. If you exported DIN_PEOPLE_ROLLUP, FIELD_INDEX, FIELD_RECORD_ORGS or another field setting before din field start, put that line in field.env. A field run from your own systemd unit with EnvironmentFile= is unchanged. 2. A custom DIN home goes in plugin.env. A DIN_HOME or DIN_INSTALL_ID_FILE set only in your shell, a service's environment or console.env no longer moves din, din status or the console. Put DIN_HOME=/your/path in ~/.din/plugin.env (install.sh already does this for a custom home), or DIN_TRUST_ENV=1 there to keep the environment's value.
From 1.0.38 to 1.0.39
1.0.39 was the release before this one. The steps above are the whole upgrade. Your records, token, settings, fields, routes and licence are kept. What is new, and the one thing to do:
1. Turn on autostart, on a paid plan. From 1.0.39 a paid entitlement is good for 14 days from its last check-in, and is bound to the install. After upgrading, run:
din activate --renew
din autostart on
din activate --renew checks in once and mints the install id (~/.din/install-id, a random number derived from nothing about you). din autostart on starts the field at login and, on a paid install, checks in for you: on Linux with systemd, the user units din-field.service and din-renew.timer (2 minutes after login, then daily); on a Linux desktop without systemd, an XDG autostart entry that checks in at each login. It is per user and needs no admin. din autostart status says what it made and din autostart off removes exactly that. Without it, din field start and din console check in quietly once a day; from day 7 without a check-in din license and the console warn, and after 14 days the install reads as Free until it checks in. On Free there is nothing to renew, and din autostart on only starts the field at login.
2. A hand-set field token must be 16 characters or more. The installer's token is 64 characters and is kept. If you put a shorter FIELD_TOKEN in field.env yourself, the 1.0.39 field refuses to start: see Troubleshooting.
3. What changes for you:
- The field count is enforced. Past your plan's fields,
din field newrefuses, makes nothing and exits 3. Fields you already have keep working, anddin field listsaysOVER PLAN.din field new <name> --dry-runasks without making anything. See Plans. - Free is up to 3 people stamping a field. A fourth new name's stamp is refused; see Use DIN as a team.
- The field answers only to
127.0.0.1,localhostor[::1], andFIELD_BINDmust be a loopback address. Open the console athttp://127.0.0.1:<port>/. din dep-audit --enrichsends nothing by default and needs the library catalog, which now expires: see Dependencies.- Re-grades land only from this release's programs. The installer puts
producer-allow.txtbeside the programs; keep it there. With 1.0.39 the same file is served at/download/producer-allow.txt, besideSHA256SUMS, which lists its sha256. - The installer stages the new programs in
bin/.newand keeps the ones it replaced inbin/.prev, so a failed copy replaces nothing. The download carries twelve programs:din-regradeanddin-libcatalogjoin the ten. DIN_B6=0no longer turns the personal-content filter off. Only--b6-offdoes.
The changelog has the full list.