What changed, and why it matters
This is a minor GitHub Actions workflow change. It ensures that a code-coverage report is uploaded even if earlier test steps failed. It does not change the Trezor firmware code, cryptography, or device behavior, and has no direct security relevance.
No security action required. Treat as a routine CI maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit adds if: always() to an actions/upload-artifact step in .github/workflows/core.yml. This causes the coverage HTML report artifact to be uploaded regardless of whether preceding job steps succeeded or failed. It is purely a CI observability improvement.
Changed components
.github/workflows/core.ymlInspect captured patch +1 / −0
diff --git a/.github/workflows/core.yml b/.github/workflows/core.yml
index 7e141ead0..dd3dd3299 100644
--- a/.github/workflows/core.yml
+++ b/.github/workflows/core.yml
@@ -669,6 +669,7 @@ jobs:
path: core/htmlcov
retention-days: 7
include-hidden-files: true
+ if: always()
core_ui_comment:
name: Post comment with UI diff URLs
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.