Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: consider adding asset that contains checksums #457

Closed
ee7 opened this issue Oct 24, 2021 · 0 comments · Fixed by #552
Closed

build: consider adding asset that contains checksums #457

ee7 opened this issue Oct 24, 2021 · 0 comments · Fixed by #552
Assignees
Labels
kind: build Non-.nim changes that affect the release binary

Comments

@ee7
Copy link
Member

ee7 commented Oct 24, 2021

No description provided.

@ee7 ee7 added the kind: build Non-.nim changes that affect the release binary label Oct 24, 2021
@ee7 ee7 self-assigned this Apr 11, 2022
@ee7 ee7 closed this as completed in #552 Apr 13, 2022
ee7 added a commit that referenced this issue Apr 13, 2022
For the configlet 4.0.0-alpha.37 release, this file would contain:

    64e801c83569759a0f877791fe0138fecbb3386eeb7167fd25a5e8f9624dda49  configlet-linux-64bit.tgz
    6ad208cd881c048e42146dfc183cf4772b3ce4609460062b3ff4c67d856df81d  configlet-mac-64bit.tgz
    48c521bb514ea8af2bb91c1129e68c9e90dfa2218b732ddce5c34372a99013b1  configlet-windows-64bit.zip

A user can download the checksum file and a release archive, and then
verify the archive was downloaded correctly. For example, on Linux:

    $ sha256sum --check --ignore-missing configlet_4.0.0-alpha.37_checksums_sha256.txt
    configlet-linux-64bit.tgz: OK

In the future, we can consider signing this file.

Closes: #457
Refs: #548
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: build Non-.nim changes that affect the release binary
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant