Bump reflex-release to 0.1.0a4 and sync workflows

[masenf]

Upgrades the pinned reflex-release version from 0.1.0a3 to 0.1.0a4 across all release workflows and configuration files, and regenerates workflows with reflex-release sync.

Summary

This change updates the release tooling to a newer alpha version that includes critical fixes for job-level status functions in the publish workflow and improved health checks in the changelog detection workflow.

Key Changes

• Version bump: Updated reflex-release pin from 0.1.0a3 to 0.1.0a4 in:

  • pyproject.toml ([tool.reflex-release] cli-command)
  • Makefile (RELEASE_VERSION)
  • All generated workflow files (.github/workflows/*.yml)

• Workflow fixes in publish.yml:

  • Added explicit status functions (!cancelled() && needs.<job>.result == 'success') to publish and tag-and-release jobs
  • These prevent implicit transitive success() evaluation that would allow skipped jobs to pass through when they should have run
  • Critical for this repository since custom-build replaces the tool's own build job, making the implicit logic dangerous

• Improved health checks in release_from_changelog.yml:

  • Refactored leg validation into a check_leg() function that distinguishes between legitimate skips (no packages to publish) and problematic skips (packages existed but job was skipped)
  • Now correctly fails when a job is skipped despite having work to publish
  • Captures detect output (ANY variable) to determine whether each leg should have run

• Documentation update in spec/process/production-readiness.md:

  • Updated version references and documented the two job-level if fixes that landed in 0.1.0a4
  • Clarified the load-bearing nature of these fixes for repositories using custom-build

Implementation Details

The status function fixes address a subtle GitHub Actions behavior: without explicit if conditions, GitHub evaluates an implicit success() over the entire transitive dependency closure rather than just direct needs. In this repository's case, the tool's own build job never runs (replaced by build_release_artifacts.yml), so it would silently pass through the collect job and allow publish to proceed without uploading anything.

The health check improvements ensure that release_from_changelog.yml correctly distinguishes between:

• A job that was legitimately skipped because detect found no packages for it (healthy)
• A job that GitHub skipped despite having packages to publish (error)

https://claude.ai/code/session_01WQwrMGQWRmvM2hMQ1PpWEg

Summary by CodeRabbit

• Bug Fixes

  • Improved release status reporting so skipped publishing steps are handled correctly.
  • Prevented release completion when required publishing work is incomplete.
  • Added stronger checks for successful release-stage outcomes.

• Chores

  • Updated release tooling to version 0.1.0a4 across project automation.

• Documentation

  • Updated production-readiness guidance to reflect current release validation behavior.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 350af696-0350-4fd0-85ea-82f6a51a2464

📥 Commits

Reviewing files that changed from the base of the PR and between ab7377d and 88500db.

📒 Files selected for processing (7)

• .github/workflows/changelog.yml
• .github/workflows/dispatch_release.yml
• .github/workflows/publish.yml
• .github/workflows/release_from_changelog.yml
• Makefile
• pyproject.toml
• spec/process/production-readiness.md

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.

---

📝 Walkthrough

Walkthrough

The release tooling pin changed from 0.1.0a3 to 0.1.0a4. Publish and tag jobs now require successful direct dependencies. Changelog release reporting now rejects skipped publish legs when packages were detected.

Changes

Release pipeline updates

Layer / File(s)	Summary
Align reflex-release version pins .github/workflows/changelog.yml, .github/workflows/dispatch_release.yml, .github/workflows/publish.yml, .github/workflows/release_from_changelog.yml, Makefile, pyproject.toml, spec/process/production-readiness.md	Workflow commands, local configuration, and release documentation now use reflex-release version 0.1.0a4.
Gate publish and tag jobs .github/workflows/publish.yml	The publish job requires successful, non-cancelled collection. The tag-and-release job requires successful, non-cancelled publishing.
Validate release leg outcomes .github/workflows/release_from_changelog.yml, spec/process/production-readiness.md	Release reporting checks skipped publish legs against detected package work and reports pending or failed legs as errors.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Merge Risk: ⚪ Minimal · up to 88500

This change updates release tooling pins and generated workflow behavior; no actionable merge-blocking risk remains beyond normal checks and review.

Sequence Diagram(s)

sequenceDiagram
  participant CollectJob
  participant PublishJob
  participant TagAndReleaseJob
  CollectJob->>PublishJob: Successful, non-cancelled collect result
  PublishJob->>TagAndReleaseJob: Successful, non-cancelled publish result
  TagAndReleaseJob->>TagAndReleaseJob: Push tag and create release

Loading

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main changes: updating reflex-release to 0.1.0a4 and synchronizing the workflows.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (7 skipped: 7 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/reflex-release-pin-update-6mowdx

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codspeed-hq]

Merging this PR will not alter performance

✅ 109 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing claude/reflex-release-pin-update-6mowdx (88500db) with main (ab7377d)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩