{
  "metadata_version": 1,
  "version": "0.9.12a",
  "channel": "stable",
  "codename": "Handshake",
  "released": "2026-09-27",
  "artifact": "canectic-0.9.12a.zip",
  "sha256": "e1f839faadf4ca76d3b5d458070907dd562da45616b66cde83b1ce611b9434e1",
  "delta": false,
  "base": null,
  "base_artifact": null,
  "min_upgrade_from": "0.9.0a",
  "node_min": "22.0.0",
  "migrations": [
    "0001-menu-layout",
    "0002-msgid-tuple-split",
    "0003-qwk-conference-blocks",
    "0004-settings-provenance",
    "0005-refresh-stale-version",
    "0006-normalise-body-text",
    "0007-netmail-seenby-text",
    "0008-qnet-role-dirs"
  ],
  "steps": [],
  "notices": [
    {
      "level": "info",
      "text": "Messages already received keep trailing spaces that make the last word of a line wrap onto a line of its own at 80 columns, most of all in OTHERNETS, until they are rendered again. Run node src/tools/maintenance.js --regen-html with the worker running (add --area SHORTCODE to do one area first), even if you ran it after updating to 0.9.11a. It changes nothing but how stored messages are displayed.",
      "id": "regen-html-trailing-padding"
    },
    {
      "level": "info",
      "text": "QWK packets now live in one directory per link and role: qnet/<ID>.hub/ for a system that is your hub, qnet/<ID>.node/ for one that is your node. The update moves what is already in qnet/ and leaves qnet/<ID> as a link to the node directory, so a Synchronet node calling through qnet-directory.js keeps working. When you next change that node's call-out, point it at the qnet/<ID>.node path shown on its connection in the peer page.",
      "id": "qnet-role-dirs"
    },
    {
      "level": "warning",
      "text": "A board with more than one QWK connection on the same network now passes messages between them: a message from one system goes to every other system on that network it has not already been through, as a Synchronet hub does. This is what a QWK hub needs, but if your board is a node of two hubs carrying the same conferences, each hub will now receive the other hub's messages. Check your QWK connections under Peers before updating.",
      "id": "qwk-pass-between-connections"
    },
    {
      "level": "info",
      "text": "Your board now relays QWK netmail for other systems on the same QWK network, as Synchronet does, and returns what it cannot deliver to its sender as BADADDR. To stop it, untick Relay QWK netmail on the network. Every decision is recorded in the Netmail Relay Log.",
      "id": "qwk-netmail-relay-default"
    },
    {
      "level": "info",
      "text": "QWK IDs are now checked against Synchronet's rules. If any of your connections or networks use an ID Synchronet would not accept, or two connections share one, you get a notification after the update naming them. They keep working; see QWK IDs in docs/sysop/QWK_NETWORKING.md for what to change.",
      "id": "qwk-id-audit"
    }
  ],
  "files": 1118,
  "bytes": 26019283,
  "full_files": 1118,
  "full_bytes": 26019283,
  "notes": null
}
