ci: publish GA artifacts only from stable tags #9

2026-10-21T06:07:40Z

KofTwentyTwo commented

2026-10-21 06:07:40 +00:00

(Migrated from github.com)

Main pushes were routed to GA publication, so a CI-only merge could fail for lack of a release tag or try to re-upload an immutable version. The shared QBit profile now tests main pushes and publishes GA artifacts only for stable vX.Y.Z tags. Snapshot and release-branch RC publication remain enabled.

Applied consistently to the eight consumers with this legacy policy. Validation used the orb's canonical caller/manifest validators and generated pipelines for main, feature, develop, release, stable tag and prerelease-tag cases. Main runs tests, develop publishes snapshots, release branches publish RCs, stable tags publish GA, and prerelease tags do not enter GA publication. Hosted checks must pass before merge.

Main pushes were routed to GA publication, so a CI-only merge could fail for lack of a release tag or try to re-upload an immutable version. The shared QBit profile now tests main pushes and publishes GA artifacts only for stable vX.Y.Z tags. Snapshot and release-branch RC publication remain enabled. Applied consistently to the eight consumers with this legacy policy. Validation used the orb's canonical caller/manifest validators and generated pipelines for main, feature, develop, release, stable tag and prerelease-tag cases. Main runs tests, develop publishes snapshots, release branches publish RCs, stable tags publish GA, and prerelease tags do not enter GA publication. Hosted checks must pass before merge.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-wms#9