ci: migrate to shared release and promote workflows#46
Merged
Conversation
TeddyAndrieux
approved these changes
Jul 13, 2026
Replace the inline tag-computation and GitHub-release logic with the reusable workflows from scality/workflows@v2.9.1. A quality-gate job now runs the test suite against the exact commit being tagged: for a Go library the tag is the artifact, so this is the only verification point. The release title now defaults to the tag alone (previously "Go-errors vX.Y.Z"), following the shared workflow convention.
ezekiel-alexrod
force-pushed
the
ci/adopt-shared-release-promote
branch
from
ba3d8dd to
a4b04a9
Compare
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
2 participants
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.
Summary
Migrate the release flow to the shared reusable workflows from
scality/workflows (
@v2.9.1),replacing the inline implementation:
release.yaml: tag computation (semver bump, alpha/beta/GA) and tagpush now come from the reusable
release.yaml.promote.yaml: the GitHub Release creation now comes from thereusable
promote.yaml.quality-gatejob runs the test suite before tagging: for a Golibrary the tag is the artifact, so this is the only verification
point.
Behavior changes
v1.2.3) instead of"Go-errors v1.2.3", per the shared workflow convention.
(
git tag --merged HEAD --sort=version:refname): an out-of-orderhotfix tag can no longer be picked as the base version.
Same migration as scality/raidmgmt#81.