Skip to content

MMX 0.2.0

Latest

Choose a tag to compare

@github-actions github-actions released this 18 Nov 05:43
· 3 commits to main since this release

MMX 0.2.0 adds a way to let your coding agent run MMX without seeing the vault passphrase, a plain summary at the top of each report, and safer first contact with a new server.

New

  • mmx secrets write-passphrase-file: run it once in your own terminal. It checks the passphrase against the vault and saves it in a file only your account can read, so your coding agent can run mmx dryrun and mmx run with MMX_VAULT_PASSWORD_FILE.
  • mmx secrets show and mmx secrets pipe-to, and nested secrets in the vault.
  • Every run, dryrun, results and status report starts with one plain line per server: what changed or would change, what is not checked yet and why, what is unchanged, and what failed.
  • wait_for_apt_lock_at_most on apt_package and apt_downloaded_package_files. apt tasks now wait up to 15 minutes for apt's locks, long enough for the update a new cloud server runs at first boot.

Changed

  • A dryrun on a new server installs only MMX's runner and connects over SSH. The first mmx run sets up MMX's HTTPS service, and says so first.
  • mmx secrets set prints one line naming the key and the vault. It never prints the value.
  • The new-vault prompt asks for a new passphrase, not one you use elsewhere.

Fixed

  • Security fixes from a whole-codebase review, including the trust of secret records read back from a node and stricter path handling.
  • dnf_package handles packages that obsolete others.

Nothing in your project files needs to change.