{
  "id": 6334560,
  "title": "myna 0.15.0: myna update",
  "url": "https://urgent.news/2026/09/08/myna-0-15-0-myna-update",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-08T21:51:18.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/chovy/myna-0150-myna-update-4dhc"
  },
  "original_language": "en",
  "account": "The myna update tool reached version 0.15.0 with several notable improvements. An in-place self update was introduced, allowing the binary to replace itself with a newer release. This update process involves comparing versions numerically to ensure correct installation order. It also selects an appropriate asset based on the machine's specifications, avoiding compatibility issues. The download is verified against the published SHA256SUMS before installation. The update is executed by a background daemon, staged in the destination directory, and renamed over the target file to prevent issues like truncation or atomicity. The --check flag can be used to report and exit when an update is waiting. Users can also specify a specific release using the --version flag. The tool remains compatible with various operating systems, including Linux, macOS, and Windows.",
  "summary": "myna 0.15.0: myna update I typed myna update today and got Unknown command \"update\". Run: myna help . That is a fair answer and a bad one. The installer already knew how to put a myna binary on a machine correctly, so there was no reason the binary could not do the same thing to itself. myna update # replace this binary with the newest release myna update --check # only say whether one is waiting…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}