Skip to content

RELEASE.md

Latest commit

 

History

History
42 lines (32 loc) · 1.5 KB

RELEASE.md

File metadata and controls

42 lines (32 loc) · 1.5 KB
Raw

Release Guide

Releases are automated via GitHub Actions when a semantic version tag is pushed (e.g., v1.0.0).

How to Release

# 1. Checkout main
git checkout main && git pull

# 2. Create & Push Tag
git tag v1.0.0
git push origin v1.0.0

This triggers the Release workflow which:

  1. Builds Docker images for all 7 services (Backend + Frontend).
  2. Pushes tags: v1.0.0, v1.0, v1, latest, and sha-<commit>.
  3. Scans images with Trivy.
  4. Creates a GitHub Release with changelogs.

Manual Release

Go to Actions → Release - Build and Publish All Services → Run workflow → Enter version (e.g., v1.0.0).

Artifacts

All images are published to ghcr.io/openndx/ (previously ghcr.io/openndx/openndx-core/; existing tags under the old path remain available but are no longer updated):

Category Service Image Name
Backend Portal Backend portal-backend
Policy Decision Point policy-decision-point
Consent Engine consent-engine
Orchestration Engine orchestration-engine
Frontend Admin Portal admin-portal
Consent Portal consent-portal
Member Portal member-portal

Verification

docker pull ghcr.io/openndx/portal-backend:v1.0.0