Record the release
When your pipeline deploys, it sends the environment, the repo and the commit hash. One CLI command, a GitHub Action or GitLab CI step, a Terraform resource, or an API call. The release is on the log before the deploy finishes.
Send the repo and commit hash when you release. OpsMinder pulls the commits from GitHub or GitLab and keeps a change log per environment. Start a freeze, and releases are rejected until it lifts.
When your pipeline deploys, it sends the environment, the repo and the commit hash. One CLI command, a GitHub Action or GitLab CI step, a Terraform resource, or an API call. The release is on the log before the deploy finishes.
Connect GitHub or GitLab once. For each release, OpsMinder pulls the commits since the previous release to that environment and shows them under it. "What went out on Wednesday?" is a page, not a search through CI logs.
Pick the environment, an end time and a reason. The team gets the message. While the freeze is on, a release to that environment is rejected and the pipeline step fails with the reason. A hotfix can still go out with an override and a reason, which is recorded on the log.
Releases, freezes, rejections and overrides sit on one timeline per environment. Each release posts to the channel you chose, so the team knows what shipped without asking. The log exports as CSV or JSON.
Free for one developer. €1 per seat a month after that.