Release Files
Part of the MountDev Ops Workspace documentation. Updated November 17, 2026
MountDev Ops Workspace documentation | Updated November 17, 2026
Our Commitment MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
A Release File is a file your account stores with its SHA-256 and a signature made with your account's own signing key. An app that downloads it can check that it came from your account and was not changed on the way. Every account has them. They are for an account that ships software to its own installs (see Installs and Signed Calls); an account that does not never sees them.
There is no Release Files screen and no button. A workflow step makes a Release File, and its own page in Files shows a small Release File label with the version. Hover over the label to see the SHA-256. No other file in Files changes.
What Makes a Release File
A Release File has a name, a version, the file's SHA-256, its size, and a signature. The SHA-256 is worked out from the stored file when the release is made, never taken from the step that asked, so the signature only ever covers what is really stored.
- A version is numbers, letters, dots, and dashes, such as
1.4.0. - A file can be up to 25 MB.
- A name and version are made once. Making the same name and version again from the same file gives the release you already have. With different contents it is refused with "Version 1.4.0 already exists with different contents. Use a new version."
- A release is never changed or deleted, and its stored file is never replaced.
- The account needs its signing key first (an owner makes it in Settings, Connections). Without it the release is not made, and the step says so.
The Signature
The signature is Ed25519, made with the account's current installs signing key. It covers these lines, joined by a newline: MDO1-REL, the file's name, the version, the SHA-256 in hex, the size in bytes, and key:<number>. The app checks it with the public key named by key, which it gets when it pairs and from GET me (see Installs and Signed Calls).
The signature is made when the release is made and made again with the current key every time the file is handed out, so rotating the key never leaves an old release that cannot be checked. The private key is opened only to sign one text and is never shown, returned, logged, or exported.
Get a Release Link
A workflow step, Get a release link (action core.release_link), gives an app a way to download one release. Choose:
- Release: one of your Release Files.
- Install: one of your installs that has proved its address.
The step hands the next step these values, which a Call an Install step can send to the app's update route: url, sha256, version, size, name, and signature.
The link:
- works for one release and one install, and for one hour;
- needs no sign-in, because an app cannot sign in;
- is checked again when it is used: the release must exist, its file must still be kept, and the install must still be active (a link for an install you ended stops working at once);
- sends the file as a download and nothing else, and lists nothing.
Each download counts as File downloads in Usage. It is not billed, and nothing about who downloaded is kept. A test run checks the step and makes no link. The step is for people and workflows only: a workflow an AI agent saves is saved turned off, and an agent never makes a link or uses the signing key.
What an App Checks
Before an app replaces itself with a download, it should check:
- the SHA-256 of what it downloaded equals
sha256; - the signature, with the public key named by
key, over the lines above; - the time: it should act only on a link it was just given.
Whatever fails, the app keeps the copy it has.
