* Checksums - Allow anyone to confirm source and delivered code
For now this only has the initial step on making CSP stricter so we can use it to parse through used files.
Very much WIP for now, but now it should just be a matter of writing up concise docs on how to go through the process, after generating and publishing the checksums via CI as well.
Related to #331
* Lint!
* Add more instructions and CI to build checksums.
* Fix typo and lint
* Remove CSP package dependency, build it manually.
Update commands in docs, fix web extension release.
* Tweak docs and webpack. CI still isn't producing a matching checksum, though.
* Tweak docs for web checksums, add debugging in the checksum action, make it faster, temporarily.
* Fix web checksum, add checksums and instructions for everything else
Closes#467
* Fix tauri release + macos sha256sum
* Remove .app checksum, since it's a directory and checksum'ing the .tar.gz seems strange.
* Properly indent + fix sha256sum results (and windows line endings problem)
* Include PWA for release, add instructions to change filenames when checksum fails.
* Include _everything_ in the CSP now, and tweak the verification script and checksum build to also include everything, now.
Still requires changes in the way to verify a published web app, where I'll have to write a script to parse through the whole CSP now.
* Add TypeScript (Deno) script to parse through CSP and download matched files.
Also update docs.
* Tweak web checksum examples.
* Remove content hashes from font files.
* Try sorting files before adding to CSP, to enforce consistency.
This implements `.nvmrc` and `.npmrc` files, as well as locking `package.json` versions, in order to get us closer to reproducible builds and more stable environment.
Closes#320
Bruno Bernardino
Martin Kleinschrodt