Skip to content

Add a release workflow - #16

Merged
ravikiranvm merged 3 commits into
mainfrom
ops-4863-release-workflow
Sep 21, 2026
Merged

ravikiranvm merged 3 commits into
mainfrom
ops-4863-release-workflow

Conversation

@ravikiranvm

@ravikiranvm ravikiranvm commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

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.yml promotes the image when a GitHub release is published, but nothing has ever created a release. This adds the missing half.

release.yml is a workflow_dispatch from main, shaped like the openops, tables and analytics release flows:

  • version input, defaulting to the next patch after the latest tag (same pinned semver action as openops); set it to bump minor or major
  • bare semver tags, no v prefix (publish.yml already tolerates one)
  • refuses an existing tag
  • logs in with the release identity under the release environment (required reviewers are the approval gate) and checks openops-mcp:<sha8> exists in the private registry, so the promote job has a source
  • creates a draft GitHub release (draft input, default true); publishing it triggers the existing promote job

pyproject.toml keeps version = "0.2.0" with a comment that it is informational, the way openops treats package.json and helm-chart treats Chart.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, since main requires pull requests.

First release: there are no tags, so a blank version would produce 0.0.1. Run it with version=0.2.0.

Testing Checklist

  • Workflow YAML validated locally
  • Not run end to end yet: the first run will be the 0.2.0 release once this merges
  • Reviewer to confirm the release identity holds Data Reader on the private registry (the promote job's comment says it does)

Copilot AI lite review requested due to automatic review settings September 21, 2026 10:53
@linear

linear Bot commented Sep 21, 2026

Copy link
Copy Markdown

OPS-4863

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 Medium severity

Open (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.

Comment thread .github/workflows/release.yml Resolved
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
ravikiranvm force-pushed the ops-4863-release-workflow branch from a4140e3 to 13443e9 Compare September 21, 2026 11:18

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 Medium severity · 1 Low severity

Open (2)
Resolved since last review (1)

Comment thread .github/workflows/release.yml Resolved
Comment thread .github/workflows/release.yml Resolved
@ravikiranvm
ravikiranvm merged commit a701d16 into main Sep 21, 2026
8 checks passed
@ravikiranvm
ravikiranvm deleted the ops-4863-release-workflow branch September 21, 2026 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants