Skip to content
This page View Markdown Open in ChatGPT Open in Claude
Minor release · November 2026

API Maker v4.1.0

Your pipeline can now upgrade the engine with one call, bundles upload much faster, and your repository holds only what you commit.

1Feature 2Improvements 1Security fix 2Breaking changes
Upgrade by API Deploy API Maker

Features

  • Upgrade or downgrade the engine from your pipeline. The Upgrade/Downgrade Engine page now makes webhooks : one call with a version, and every server installs it, restarts on it and goes back if it can not start. Ask how it goes with a second call, try it with dryRun, limit who may call it, and see every call on the page. Webhooks stay on your server : they are not part of git commits, pulls or pushes. Upgrade by API →

Improvements

  • Bundles upload much faster. Up to six pieces go at once, a panel on plain HTTP encrypts them about five times faster without freezing the page, the servers no longer read the whole bundle twice, and the page shows the speed and the time left. If the connection drops, or a deployment fails, click Upload again : only what is missing is sent. Upload a package →
  • Panel headers line up. Titles, icons and buttons in the headers of the panel pages sit on one line, at one height, in both themes.

Security fixes

  • Second factors stay out of Git. A commit could write the TOTP secret and the recovery codes of the admin user to the repository. It no longer does, the next commit removes them, and a pull never reads them. Old commits still hold them : if others can read your repository, turn two-factor off and on again. What goes to Git →

Breaking changes

  • API user passwords live in your secret. The Add API User dialog has no password field and no switch any more : you select a Password Path, a key of your default secret. The API of the panel asks for apiUserPasswordPath and refuses password. API users with a typed password keep signing in until you edit them. API users →
  • API Maker commits only when you ask. A connected local client no longer makes the backend commit the security report to your repository, and its switch is gone. Launchpad no longer pushes every item when it sets a folder up : the local client brings them into the folder, and you commit when you want. Automatic scans still keep the report fresh on your disk : commit it from the Git page when you want it there. Automatic scans →