Use a valid name for the activation artifact#54146
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
|
Hey ✅ Focused — Single, well-scoped change: renaming ✅ Tests included — New ✅ Golden fixtures updated — All test data consistently reflects the rename across ✅ Clear purpose — Directly addresses #54114 (incident report) with minimal risk. The PR looks ready for final validation and merge. Since you've marked the security checks and verification as pending, make sure those complete before pushing. Nice quick turnaround on a critical incident fix! 🚀
|
PR TriageCategory: bug | Risk: medium | Priority: high (score 65/100)
|
PR TriageCategory: Fixes activation-artifact upload failure (invalid name). Draft — needs undraft before merge. Overlaps with #54117 (same root cause, alternate fix). Automated triage — see the [triage report issue] for full context.
|
|
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Renamed the artifact to |
|
/scout investigate recent failure to determine if this was a transient failure. |
|
🏕️ Lost in the wilderness! Scout failed. Sending search party... Warning Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding. What happenedThe threat detection engine failed to produce results. Review the workflow run logs for details.
|
|
/q set the deepwiki MCP as required false in scout to fix it. |
|
🔧 Pay attention, 007! Q is preparing your gadgets for this issue comment... |
|
🍳 skillet has started processing this pull request comment |
GitHub Actions began rejecting the reserved artifact name
activation, causing activation jobs across the smoke-test fleet to fail before agent execution.activation-artifact.