Fix v0.2.4 Winget checksum#7
Conversation
|
@coderabbitai[bot] review |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Winget installer manifest for ChangesInstaller manifest
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
✅ Action performedReview finished.
|
|
Package Seeds passes on the focused branch. The remaining upstream CI failures match the current baseline and are addressed by #6 (network timeout, sanitizer/runtime UB, cross-target POSIX declarations, and the claims gate). The checksum commit integrated after #6 passes all 11 CI jobs: https://github.com/attahn/mako/actions/runs/29692077948 |
11ca8d4 to
5e8d54a
Compare
Updates the v0.2.4 Winget installer checksum to match the published Windows release asset. The manifest retained the v0.2.3 checksum, causing Package Seeds validation to fail.
Tests:
bash scripts/publish-winget-seed.sh; Package Seeds passed.Summary by CodeRabbit
loreste.makoversion 0.2.4 by refreshing the SHA-256 checksum used to validate the installer, keeping all other metadata unchanged.