A release is one version of your app, like 2.5, as it moves across your environments. The Releases page shows what you ship, where it is, and what was found in it. For the idea behind it, see Releases.
Create a release
There are three ways. Use the one that fits how you deploy.
- By hand. On Releases, click New Release. Give it a name (for example
2.5), pick where it is now, and add notes if you like. - From CI. Send
releasefrom the GitHub Action or the CI runs API. Certyn creates the release if it is new and records that it is on that environment now, before the run starts. - From GitHub deploys. With the Certyn GitHub App, a deploy that names its version records it. A plain commit never creates a release.
Record a deploy
On a release's page, the Environments panel shows where it is: Here now or Moved on. Click Record deploy to say the release is on another environment now.
Recording a deploy counts as a version change. Suites with Run on version change turned on for that environment start. See Scheduling and Automation.
A release counts as shipped the first time it reaches a production environment.
Read a release
The release page has:
- What is in it: the notes.
- Found in this release: findings first seen on this release.
- Runs: suite runs and single runs on this release.
- Open from earlier releases: open findings from older releases that nobody checked again. They are kept apart, so they are not blamed on this release and not hidden either.
The header's environment narrows all of it.
What the status means
Certyn lists what it knows. People decide when a release ships.
| Status | When |
|---|---|
| Blockers found | An open critical or major finding was found in this release, or a run on it failed |
| Risks to review | No blockers, but there are open minor findings, or open findings from earlier releases |
| No known blockers | Runs finished and nothing above was seen |
| Not tested yet | No finished runs on this release |
| On the agenda | The release has agenda items. Certyn shows how many are done and how many saw a problem, and gives no verdict |
Plan the testing for a release
Ask in the chat on Home, for example plan testing for 2.5. Certyn drafts a plan with you and saves it once you agree. It works like the Agenda.
To check a release before you ship, use /release in the chat. Certyn lists blockers, risks and missing checks, each with its evidence. See Assessing release readiness.