Repository navigation
Add a release workflow - #16
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The release workflow does not enforce its main-only dispatch contract, allowing non-main commits to be released.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
What changed in this PR
Adds a manual release workflow that validates the project version and private image before creating a GitHub release for public image promotion.
Changes:
- Added version, lockfile, tag, and image checks.
- Added draft release creation and promotion instructions.
- Documented the release process.
| File | Description |
|---|---|
.github/workflows/release.yml |
New release workflow |
.github/workflows/publish.yml |
Updated promotion documentation |
README.md |
Added releasing instructions |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Nothing created releases so far: publish.yml promotes the image when a release is published, but the tag and release themselves were a manual step, and no version was ever released. The workflow follows the openops, tables and analytics release flows: the version is a dispatch input defaulting to the next patch after the latest tag, tags carry no "v" prefix, the run is gated by the release environment, and the release is created as a draft. Before tagging it checks the commit's image exists in the private registry, since the promote job imports rather than rebuilds. The version in pyproject.toml is informational, as nothing reads it, and is not bumped by a release; the file says so. Part of OPS-4863. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
ravikiranvm
force-pushed
the
ops-4863-release-workflow
branch
from
September 21, 2026 11:18
a4140e3 to
13443e9
Compare
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The release workflow has a fail-open tag check and an incorrect draft-release URL rewrite.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
Open (2)
Resolved since last review (1)
MarceloRGonc
approved these changes
Sep 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Part of OPS-4863.
Additional Notes
The OSS docker compose deployment (openops-cloud/openops#2521) pins
openops.azurecr.io/openops-mcp:0.2.0, which does not exist yet:publish.ymlpromotes the image when a GitHub release is published, but nothing has ever created a release. This adds the missing half.release.ymlis aworkflow_dispatchfrommain, shaped like the openops, tables and analytics release flows:versioninput, defaulting to the next patch after the latest tag (same pinned semver action as openops); set it to bump minor or majorvprefix (publish.ymlalready tolerates one)releaseenvironment (required reviewers are the approval gate) and checksopenops-mcp:<sha8>exists in the private registry, so the promote job has a sourcedraftinput, default true); publishing it triggers the existing promote jobpyproject.tomlkeepsversion = "0.2.0"with a comment that it is informational, the way openops treatspackage.jsonand helm-chart treatsChart.yaml. Nothing reads it: the image label is the commit sha, the API image installs with--no-install-project, and the helm chart pins by sha. Bumping it from the workflow is not possible anyway, sincemainrequires pull requests.First release: there are no tags, so a blank
versionwould produce0.0.1. Run it withversion=0.2.0.Testing Checklist