Skip to content

fix: allow partial releases when some platform builds fail#34

Merged
ronaldtse merged 1 commit into
mainfrom
fix/release-workflow-partial-releases
Feb 19, 2026
Merged

fix: allow partial releases when some platform builds fail#34
ronaldtse merged 1 commit into
mainfrom
fix/release-workflow-partial-releases

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Summary

  • Release job now runs even if some platform builds fail (partial release)
  • Individual gem push failures don't block other gems
  • GitHub releases will be created with successfully built gems

Background

The v0.5.1 and v0.5.2 releases were not created because:

  1. v0.5.1: Tag was never pushed to GitHub
  2. v0.5.2: Release job was skipped because aarch64-linux-musl build failed

When any build in the matrix fails, the entire build job is marked as failed, which causes the release job to be skipped (since it has needs: build without if: always()).

Fix

Added condition to release job:

if: always() && !cancelled() && needs.build.result != 'skipped'

This allows the release to proceed with successfully built gems even when some platforms fail.

Testing

After merging, manually trigger a release with version_bump: skip to create the missing v0.5.2 release.

- Release job now runs even if some builds fail (partial release)
- Individual gem push failures don't block other gems
- Use 'always() && !cancelled() && needs.build.result != skipped'

This ensures GitHub releases are created even when not all platforms
build successfully.
@ronaldtse ronaldtse merged commit d54148d into main Feb 19, 2026
93 checks passed
@ronaldtse ronaldtse deleted the fix/release-workflow-partial-releases branch February 19, 2026 01:26
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