Skip to content

ci: release when "CI passed" succeeds, not the whole CI - #14

Merged
darxnet merged 1 commit into
mainfrom
ci/release-after-ci-passed
Nov 19, 2026
Merged

darxnet merged 1 commit into
mainfrom
ci/release-after-ci-passed

Conversation

@darxnet

@darxnet darxnet commented Nov 19, 2026

Copy link
Copy Markdown
Owner

A failed non-blocking job (test-macos, gomysql's experimental servers) fails the called CI workflow, so the release job, which needed all of it, was skipped although "CI passed" succeeded (gomysql main, 2026-11-19, MySQL 9 cell).

  • ci.yml: "CI passed" sets the output passed=true, exposed by workflow_call as passed.
  • release.yml: the release job runs if: !cancelled() && needs.ci.outputs.passed == 'true'; it stays identical in all repos.

A failed non-blocking job (test-macos, experimental servers) fails the
called CI workflow, so the release job, which needed all of it, was
skipped although "CI passed" succeeded (gomysql main, 2026-11-19).
CI exposes the result of "CI passed" as the output passed, and the
release job runs on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@codecov

codecov Bot commented Nov 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@darxnet
darxnet merged commit d45028b into main Nov 19, 2026
10 checks passed
@darxnet
darxnet deleted the ci/release-after-ci-passed branch November 19, 2026 11:34
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