OpsWarden v1.0.7
OpsWarden can now send an email when an automation rule fires.
A Manager configures a Team-scoped SMTP connection — host, port, username,
password and sender address, all encrypted at rest — and any rule can react with
email_notify. Subject and body accept the same templates as the other
reactions, so an alert can name the workflow, repository and branch that failed.
Delivery runs through the existing durable engine, so a failure is recorded
against the connection and surfaced like any other reaction error.
The connection can be tested before use: the probe opens an authenticated SMTP
session and issues NOOP, so credentials are verified without mailing anyone.
Also in this release
- Cutting a release is now one command,
just release <version>. It rewrites
every version-bearing file, refreshes the three lockfiles that embed the
version, verifies all of them agree, then commits and tags. verify_release_version.shchecks nine values instead of five. The lockfiles
were previously unchecked, and a stale one does not fail the gate — it dirties
the working tree during the release build, which is far harder to diagnose.
Install
| Platform | Artifact |
|---|---|
| Linux (Debian/Ubuntu) | OpsWarden_1.0.7_amd64.deb |
| Linux (portable) | OpsWarden_1.0.7_amd64.AppImage |
| Windows | OpsWarden_1.0.7_x64-setup.exe |
| macOS | OpsWarden_1.0.7_aarch64.dmg |
Verify a download against SHA256SUMS. Every artifact carries a GitHub
build-provenance attestation.
Server image
ghcr.io/opswarden-git/opswarden-server@sha256:e6e1d4483d6074a4ac5037d338a66ca2913f60dd671f0f3286bcd8a881aa0e6c
Production pins this digest, never a mutable tag.
What's Changed
- Remove remaining pedagogical comments by @RomeoCavazza in #114
- feat(automation): implement resilient timer triggers (Run 3) by @RomeoCavazza in #115
- feat(automation): add the Email REAction vertical (Run 4) by @RomeoCavazza in #116
- chore(release): script the version bump and cover the lockfiles by @RomeoCavazza in #117
Full Changelog: v1.0.6...v1.0.7
