Feature
Releases: versions bound to real git tags
What is in a version, which checks ran and when it went live — bound to a git tag instead of typed into a spreadsheet. Developer plan.
A release in Zuuna is not a note, it is a version hanging off a real git tag. It knows which cards went with it, which commits are behind them, which checks ran — and when it actually went live.
The pipeline on one page
Staging and production side by side, each with its state and timing: built in 2 minutes, deployed in 15 seconds, live at 21:15. Below that sit the individual checks and deploys with their outcome and the commit they ran on. That is the answer to "what is actually out there?" without anyone opening three systems.
What surfaces before you ship
Zuuna shows you what does not add up before the release goes out: work marked done with no code behind it, code with no ticket, pull requests still open. Those are precisely the three things otherwise discovered the following morning.
Shipping, with a brake
A version can be shipped straight from its page — one button, the version named out loud, and a typed confirmation before anything reaches production. Zuuna asks; your CI still builds. If an approval gate is blocking and it is 3am with nobody awake to sign off, there is a break-glass route: only for people who hold the right to approve, only with a written reason, and it stays on the record.
Afterwards
The date you promised sits next to the date you shipped, so "did we make it?" has an answer rather than a recollection. And when a version goes out, its cards can move to published automatically instead of somebody dragging thirty tickets by hand.
Plan
Developer plan — together with git on the board, the code graph, the REST API and webhooks. They belong together: releases without a git connection would just be a spreadsheet again.
FAQ
Does Zuuna deploy my code?
No. Zuuna triggers your pipeline and shows what it reported — the building still happens on your side. The button is an approval, not a build server.
What is a break-glass approval?
A documented route past a blocked approval gate: only for people who hold approval rights, only with a typed reason, and the whole thing stays visible. Built for the emergency, not for everyday use.
How does Zuuna know which cards are in a version?
From the commits between two git tags: if a commit mentions a card ID, that card belongs to the version. This is why the list freezes at publish — it describes what actually shipped.