Skip to content

ci: publish provider binaries in release-plz flow - #178

Merged
Teakowa merged 3 commits into
mainfrom
codex/issue-176-release-context
Sep 3, 2026
Merged

ci: publish provider binaries in release-plz flow#178
Teakowa merged 3 commits into
mainfrom
codex/issue-176-release-context

Conversation

@e54-bot

@e54-bot e54-bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • integrate repository-owned provider builds into the release-plz workflow
  • gate provider jobs on the shared workflow's releases_created output
  • check out and upload using the release tag from releases metadata
  • remove the separate tag-triggered provider release workflow

Validation

  • actionlint .github/workflows/release-plz.yml
  • release-flow contract assertions
  • independent ablation verification
  • git diff --check

Fixes #176

Build and publish provider archives as downstream jobs of the release-plz workflow, using its release metadata and skipping the jobs when no release is created.

Fixes #176

@Teakowa Teakowa left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Major — .github/workflows/release-plz.yml

releases_created only means release-plz released some package, while releases is an array of all released packages. This workspace has multiple packages, and release-plz returns a tag even when git-tag creation is disabled. Using releases[0].tag can therefore select a non-opy-rs synthesized tag or run the provider flow when no opy-rs GitHub Release was created.

Select the releases entry whose package_name == "opy-rs", gate the provider jobs on that entry existing, and use that entry's tag for checkout/upload.

Resolve the release-plz metadata by package name before gating provider publication, so unrelated package releases cannot trigger provider assets.

Refs #176

@Teakowa Teakowa left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Teakowa
Teakowa merged commit 10e467f into main Sep 3, 2026
5 checks passed
@Teakowa
Teakowa deleted the codex/issue-176-release-context branch September 3, 2026 18:18
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.

Publish provider binaries in the release-plz release flow

2 participants