reflex-release@0.1.0a4

Bug Fixes

• A release using a [[tool.reflex-release.custom-build]] entry no longer publishes nothing while reporting success. Exactly one of the built-in build job and a custom-build job runs for any given package, so the other is always skipped — and GitHub evaluates the implicit success() a job gets when its if names no status function over the whole transitive dependency closure, not just the direct needs. The skipped build therefore reached publish straight through the collect written to absorb it, and tag-and-release behind it: every build succeeded, the artifacts were verified and checksummed, and then the upload silently never happened. Both jobs now carry an explicit needs.<job>.result == 'success' guard. release_from_changelog.yml's report job, the canonical failure signal for a partial release, was blind to the same shape because it accepted any skipped leg; it now accepts a skipped leg only when detection found nothing for that leg to publish, so a release that publishes nothing — or holds a lockstep package back — is red.