Repository navigation
ci: align the build pipeline with aweXpect - #1130
Merged
Merged
Conversation
Publish Tests Results runs with `if: always()` and succeeds even when tests fail, so gating the push on it alone let a tag with failing tests reach nuget.org. The push now waits for the test jobs directly. Pack starts right away and only the push is gated, so benchmarks and mutation tests no longer hold up a release. The GitHub release step referenced a non-existent `steps.tag` output and now releases the pushed tag, with a warning when it fails after the packages were pushed. Actions are pinned to commit SHAs, and the workflow can be dispatched manually and queues runs per ref, as in aweXpect.
vbreuss
enabled auto-merge (squash)
October 18, 2026 06:37
|
|
This is addressed in release v7.1.2. |
This was referenced Oct 29, 2026
This was referenced Nov 11, 2026
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.
Publish Tests Results runs with
if: always()and succeeds even when tests fail, so gating the push on it alone let a tag with failing tests reach nuget.org. The push now waits for the test jobs directly.Pack starts right away and only the push is gated, so benchmarks and mutation tests no longer hold up a release. The GitHub release step referenced a non-existent
steps.tagoutput and now releases the pushed tag, with a warning when it fails after the packages were pushed. Actions are pinned to commit SHAs, and the workflow can be dispatched manually and queues runs per ref, as in aweXpect.