hackjutsu/Lepton

Provide SHASUMS of releases assets

Open

#286 opened on Apr 10, 2018

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (9,902 stars) (502 forks)batch import
help wantedwon't do but PR welcome

Description

Looks like that there are only SHASUMS for installers, in those yml files, no SHASUMS for 7z files. I added support to install lepton through scoop, from a bucket I created. Currently I need to download files (about 100MB per update) and manually calculate the hash, would be appreciated if you could provide SHASUMS for it while publishing a new release of lepton.

Contributor guide

Tech stack
javascriptelectron
Domain
release
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GitHub release processbasic shell scripting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate the existing release process, specifically the yml files that contain SHASUMS for installers. Understand how those checksums are generated and uploaded. Then, extend the process to generate and upload SHASUMS for the 7z files as well. Check the repository's build scripts or CI configuration (e.g., GitHub Actions) to see where the release assets are built and how checksums are currently computed.