A release is a version of your app, like v2.5, as it moves from one environment to the next: dev, then staging, then production. It is the same release on every environment, matched by its name.
Use the same version name on every environment, so Certyn can follow one release from start to finish.
Where releases come from
A release is created when you name a version:
- by hand, on the Releases page (New release)
- from CI, by sending
releasefrom the Certyn GitHub Action or the CI API - from a deploy: when an environment's version changes, that version becomes a release
A deploy that only carries a commit SHA does not create a release.
The release page
Open Releases and pick one. The page shows:
- What is in it: the release notes, when it has some
- Found in this release: findings first seen on this version
- Runs: the runs on this version, on each environment
- Open from earlier releases: findings from older versions that have not been checked on this one
- Environments: where the release is now, and where it was. Record deploy marks it as on another environment.
- Properties: when it shipped and the date it is planned for
A finding's Found in column tells you which release it was first seen in. When you close a finding as Fixed, you can say which release fixed it.
Planning a release
A release can have its own agenda: the checks to do before it ships. Click Plan this release, or ask in the chat. Certyn drafts the plan with you in the chat, and saves it only once you agree.
On each check, Certyn reports what it saw. It never says a release is ready; people decide.