osFoundry / Platform
Releases
Cut a release with notes, artefacts and changelog — auto-generated by Maestro if you want.
What it is
Releases is osFoundry's way to turn a point in your Git history into a shipped, versioned thing: a tag, a set of build artefacts, human-readable release notes, and a changelog. It lives in the Code & Build surface alongside your repositories, so cutting a release doesn't mean leaving the workspace, wiring up a separate CI provider, or copying commit messages into a wiki by hand. You pick the commit or tag, name the version, attach the files you built, and publish.
Inside osFoundry, the changelog and notes can be auto-generated by Maestro, the workspace's agent. Maestro reads the commit range since your last release and drafts a changelog and a summary of what changed — grouped and phrased for people, not just raw commit subjects. Because osFoundry is bring-your-own-key, that drafting runs against whatever model you've connected (local, cloud, or self-hosted); there's no reseller markup on the tokens, and if you point it at a local model the diff and commit history stay on your device. The draft is a starting point you edit, not a black box — you keep final say over every line before it ships.
This matters because release notes are the step teams skip when it's friction. Keeping the tag, the artefacts, the changelog, and the narrative in one place — next to the code they describe — means the record of what you shipped actually gets written, stays accurate, and is there when someone asks "what changed in this version?" three months later.
Key capabilities
- Tag a commit as a named version and publish it as a release from the Code & Build surface, no external CI required
- Attach build artefacts — binaries, packages, archives — to the release so the shipped files live with the version that produced them
- Auto-generate a changelog from the commit range since your last release, drafted by Maestro and fully editable before you publish
- Write release notes as a human-readable summary of what changed, kept next to the code instead of in a separate doc
- BYOK and local-first: changelog drafting runs on your own model keys, and with a local model your commit history never leaves the device
Use cases
- Solo maintainer: cut a v1.2 release, let Maestro draft the changelog from 40 commits, edit two lines, and publish with the built binary attached
- Small team lead: ship a versioned build with notes your teammates can actually read, without paying per-seat for a separate release tool
- Privacy-conscious developer: generate release notes with a local model so proprietary commit messages and diffs stay on your machine
Frequently asked questions
Does osFoundry write my release notes for me?
It can. Maestro reads the commits since your last release and drafts a changelog and a plain-language summary, which you then edit before publishing. It's optional — you can write everything by hand — and the AI output is always a draft you review, never published automatically.
Which AI model generates the changelog?
Whichever one you've connected. osFoundry is bring-your-own-key, so changelog drafting uses your own model — local, cloud, or self-hosted — with no markup on the tokens. Point it at a local model and your commit history stays on your device.
Can I attach build artefacts to a release?
Yes. A release ties together the version tag, the release notes, the changelog, and the artefacts you built — binaries, packages, or archives — so the files you shipped stay with the exact version that produced them.