Fix split language release jobs after skipped gates - #163
Merged
Conversation
Adding .gitkeep for PR creation (default mode). This file will be removed when the task is complete. Issue: #162
konard
marked this pull request as ready for review
June 8, 2026 19:49
Member
Author
Working session summaryImplemented and pushed the fix to PR 163: #163 What changed:
Verification:
PR is ready for review, not draft, merge state is This summary was automatically extracted from the AI working session output. |
Member
Author
🤖 Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
📊 Context and tokens usage:
Total: (562.7K + 10.8M cached) input tokens, 58.3K output tokens, $19.077064 cost 🤖 Models used:
📎 Log file uploaded as Repository (64054KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
Member
Author
✅ Ready to mergeThis pull request is now ready to be merged:
Monitored by hive-mind with --auto-restart-until-mergeable flag |
This reverts commit 8d62855.
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.
Fixes #162
Summary
This PR fixes the split JavaScript/Rust release workflows introduced by PR #161. The post-merge runs after PR #161 succeeded overall, but the actual language release jobs were skipped because their
needsgraph included PR-only gate jobs that are skipped onpush.The release jobs now use explicit status-check guards so GitHub Actions evaluates them after skipped PR-only dependencies:
always() && !cancelled()plus successfullintandtestresults.always() && !cancelled()plus successfullint,test, andbuildresults.Case Study
Full investigation and evidence:
https://github.com/link-foundation/command-stream/blob/issue-162-0c186d5158ec/docs/case-studies/issue-162/README.md
The case study includes the PR #161 timeline, downloaded CI logs, package registry snapshots, template snapshots, and before/after test logs.
Template Reports
The JavaScript and Rust upstream templates already protect their automatic release paths from this skipped-needs behavior. I found related workflow-dispatch risks in two other templates and opened upstream reports:
Verification
Local checks run:
The full JS suite passed with 686 passing tests, 5 skipped, 0 failed. The container did not provide
jqand passwordless sudo was unavailable, so the full local JS test run used a temporary uncommittedjq-1.7.1binary under/tmp/issue-162-bin; CI installsjqin the workflow.Release Notes
Patch release markers were added for both packages so the next merge to
mainhas release input to consume.