Skip to content

Conversation

@dantovska
Copy link
Contributor

@dantovska dantovska commented Jan 28, 2026

Summary

  • Add generate-checksums-summary.js script to parse electron-builder YAML files (latest.yml, latest-linux.yml, latest-mac.yml)
  • Output SHA-512 checksums as Markdown table in GitHub Actions job summary
  • Integrate into both staging (aws-upload-dev.yml) and production (aws-upload-prod.yml) workflows

This eliminates the need to manually navigate AWS S3 to retrieve checksum values for release notes.

Test plan

  • Trigger a staging release (push to release/* branch)
  • Verify checksums appear in GitHub Actions job summary
  • Verify format matches release notes table structure
  • Verify all platforms are covered: Windows, Linux (AppImage, deb, rpm), macOS (Intel, Apple Silicon)

Note

Low Risk
Low risk: adds a non-blocking workflow summary step that parses build metadata and does not affect build artifacts or S3 upload logic. Main risk is missing/incorrect parsing if electron-builder YAML format changes, but continue-on-error prevents workflow failures.

Overview
Adds a new .github/generate-checksums-summary.js script that parses electron-builder latest*.yml files in release/ and appends a SHA-512 checksums Markdown table to the GitHub Actions job summary (mapped to the release-notes package names and sorted consistently).

Integrates this into both aws-upload-dev.yml and aws-upload-prod.yml as a continue-on-error step so checksum reporting is best-effort and won’t block uploads.

Written by Cursor Bugbot for commit 99f7fa5. This will update automatically on new commits. Configure here.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 28, 2026

Code Coverage - Backend unit tests

St.
Category Percentage Covered / Total
🟢 Statements 92.5% 14224/15378
🟡 Branches 74.39% 4395/5908
🟢 Functions 86.23% 2198/2549
🟢 Lines 92.31% 13603/14736

Test suite run success

3056 tests passing in 290 suites.

Report generated by 🧪jest coverage report action from 99f7fa5

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 28, 2026

Code Coverage - Integration Tests

Status Category Percentage Covered / Total
🟢 Statements 80.76% 16480/20406
🟡 Branches 63.67% 7474/11737
🟡 Functions 69.4% 2298/3311
🟢 Lines 80.37% 15504/19290

@github-actions
Copy link
Contributor

github-actions bot commented Jan 28, 2026

Code Coverage - Frontend unit tests

St.
Category Percentage Covered / Total
🟢 Statements 82.85% 21179/25563
🟡 Branches 68.12% 8951/13140
🟡 Functions 78.07% 5797/7425
🟢 Lines 83.24% 20740/24915

Test suite run success

5553 tests passing in 708 suites.

Report generated by 🧪jest coverage report action from 99f7fa5

@dantovska dantovska changed the title ci: output SHA-512 checksums in GitHub workflow summary RI-7976: output SHA-512 checksums in GitHub workflow summary Jan 29, 2026
pawelangelow
pawelangelow previously approved these changes Jan 30, 2026
valkirilov
valkirilov previously approved these changes Jan 30, 2026
Add script to parse electron-builder YAML files and display checksums
in the GitHub Actions job summary for easy copy-paste to release notes.
Eliminates need to manually navigate AWS S3 to retrieve checksum values.

References: #RI-7976
@dantovska dantovska dismissed stale reviews from valkirilov and pawelangelow via 99f7fa5 February 2, 2026 07:55
@dantovska dantovska force-pushed the feature/RI-7976/output-checksums-workflow branch from 452b370 to 99f7fa5 Compare February 2, 2026 07:55
@dantovska dantovska merged commit 6116022 into main Feb 2, 2026
51 of 52 checks passed
@dantovska dantovska deleted the feature/RI-7976/output-checksums-workflow branch February 2, 2026 11:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants