Skip to content

ci: migrate to shared release and promote workflows#81

Open
ezekiel-alexrod wants to merge 1 commit into
mainfrom
ci/adopt-shared-release-promote
Open

ci: migrate to shared release and promote workflows#81
ezekiel-alexrod wants to merge 1 commit into
mainfrom
ci/adopt-shared-release-promote

Conversation

@ezekiel-alexrod

@ezekiel-alexrod ezekiel-alexrod commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Replace the local release and promote copies with the reusable workflows from scality/workflows (pinned to @v2.9.1):

  • The semver computation and tag push move to release.yaml@v2.9.1.
  • The GitHub Release creation moves to promote.yaml@v2.9.1.
  • The quality gate (go test on the exact commit being tagged) stays in this repo.

Note: the release title is now the tag alone (vX.Y.Z); pass product-name to the promote workflow to prefix it.

Part of the org-wide migration to scality/workflows (scality/workflows#108).

@ezekiel-alexrod ezekiel-alexrod requested a review from a team as a code owner July 9, 2026 12:38
Replace the local release/promote copies with the reusable workflows from
scality/workflows: the semver computation and tag push move to
release.yaml@v2.9.1, and the GitHub Release creation to promote.yaml@v2.9.1.

The quality gate (go test on the exact commit being tagged) stays in this
repo, as releases are cut from main without re-running pre-merge.

Part of the org-wide migration to scality/workflows (PR scality/workflows#108).
@ezekiel-alexrod ezekiel-alexrod force-pushed the ci/adopt-shared-release-promote branch from 298d6aa to 3b57791 Compare July 10, 2026 08:29
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.

1 participant