One page for what shipped, and the release note for what is next
Create, edit and approve the release note for a bundle of components on a page that also lists every deployment so far, live from your merge requests, with version dropdowns filled from what has actually been built.
- Best for
- Platform and delivery teams
- Front end
- Embedded in your own service
- Works with
- GitLab, GitHub, AWS, Slack
Watch a deployment go in
A public service styled with the GOV.UK Design System and built with the Flomation Embed SDK: the live deployment list, a request with real component versions, and the confirmation at the end.
Nobody can answer "what is in production?"
The answer exists, but it is spread across a pipeline UI, a cloud console, a chat thread and one engineer's memory, and asking for a deployment is a different tool again.
- Four tabs to answer one question, and a different answer depending on who looks.
- Release notes are written from memory at the end of the week, in a different format each time.
- Component versions are typed by hand, so a release is recorded against something that was never built.
- Only the people who know the pipeline can see the state, or get a release signed off.
The list and the release note, in one place
A flow supplies the live picture, the same page takes the new release note, and approval happens without leaving it. Nobody has to know which pipeline is which.
The list comes from the source of truth
The table is filled by a flow that queries your merge requests as the page loads, so the state of each deployment, open, closed or merged, is right at the moment somebody looks.
Dropdowns that know what exists
Component versions are pulled from what has actually been built and published, so a release note cannot be raised against a version that was never released.
Rendered inside your own service
The Embed SDK renders the form natively in your site, in your own design system, with no iframe. The demo uses the GOV.UK Design System, unchanged.
What a release note looks like in Flomation
One flow fills the page, another handles what was submitted, and both leave a record.
- TriggerRelease note submittedTitle, components and versions
- ConditionalValidate the bundleVersions, environment and ownership
- HumanApprovalThe owner signs the bundle off
- OutputRecorded and announcedNote published, requester emailed, channel told
One answer, always current
Stop assembling the answer by hand
Build the dashboard once and let it read from the systems that already know. The people who need a release recorded can raise one without learning your pipeline.
Get started