Fix SLSA provenance job failing with exit code 27#19
Merged
harumaki4649 merged 2 commits intomainfrom Mar 8, 2026
Merged
Conversation
…step failure Co-authored-by: harumaki4649 <83683593+harumaki4649@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix error in ci.yml configuration
Fix SLSA provenance job failing with exit code 27
Mar 8, 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.
The
provenance / finaljob was exiting with code 27 (SUCCESS=false) becauseupload-assets: truecaused the SLSA generator's internalupload-assetsstep to be skipped — no GitHub release/tag exists on amainpush, so the step is skipped, and thefinaljob treats a skipped required step as failure.Change
.github/workflows/ci.yml: Setupload-assets: falseon theprovenancejob. The downstreamreleasejob already downloads and attaches the provenance artifact (needs.provenance.outputs.provenance-name) to the GitHub Release, making the SLSA generator's built-in upload redundant.💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.