fix: use paths_released and version outputs for immutable releases#19
Merged
Conversation
thoroc
force-pushed
the
fix/release-please-outputs
branch
from
February 6, 2026 23:28
42a399f to
8b7d330
Compare
There was a problem hiding this comment.
@github-copilot Please review this PR focusing on:
- Code quality, best practices, and potential bugs
- Security vulnerabilities and unsafe patterns
- Performance implications
- Documentation accuracy and completeness
- Test coverage and edge cases
Please provide specific, actionable feedback.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem\nWhen using
skip-github-release: trueto prevent release-please from creating the release (needed for immutability), therelease_createdoutput is never set to true. This caused the build_and_upload and create_release jobs to be skipped, resulting in releases without binaries.\n\n## Solution\nUse the correct outputs whenskip-github-release: true:\n-paths_released- indicates a release should happen (set to ["."] for root releases)\n-version- the version number to construct the tag (e.g., v0.4.5)\n\n## Changes\n- Changed condition fromrelease_created == 'true'topaths_released != '[]'\n- Changed tag_name from output to constructed:v${{ version }}\n\nThis ensures the workflow runs when a release is needed and creates the release atomically with all built binaries.