v0.19.2

Hermit's installer process is fragile and this has exposed those issues.

We'll revisit this later.

Revert "fix: use the right installer URL for the canary channel (#257)"

This reverts commit f4b87be034d57952b7be5769103025609f4ff92e.

Revert "fix: publish versioned installer script to canary"

This reverts commit 8b40b968aa683352bcbac4e60867712e006efc01.

Revert "feat: verify installer checksum when bootstrapping (#253)"

This reverts commit 4802074e3e3fe4f13e8e792f939447161657f801.

v0.19.1

fix: use the right installer URL for the canary channel (#257)

* fix: use the right installer URL for the canary channel

- We make changes for the generated bin/hermit to correctly identity the
download URL for the canary channel. This part was overlooked in an
earlier implementation.
- The `InstallScriptSHAs` map is manually populated for the "canary" and
"stable" channels, respectively, in `env.go`.
- Update `ScriptSHAs` for the updated `bin/hermit` scripts, for "canary"
and "stable" channels.
- Add `InstallerSHA256Sums` map to the `Config` struct of the main Hermit app.
- Update GHA CI step for sanity check of SHA256 sums of install script.
- Fix a buggy integration test.

* Add installer-sha-256 command

This allows us to avoid inspecting the Hermit source for the CI test to
validate checksum coherence in Hermit and in geninstaller. It makes the
CI test more robust and less inelegant.

* Make installer sums app configurable during init

The default configuration for `InstallerSHA256Sum` is
`hermit.InstallScriptSHAs`. This value now can be overridden by the main
application.

* Fix test: envfixture

Provide an empty map as the extra input argument needed by hermit.Init().

* Run gofmt -s on env.go

Reformatting so it's conformant.

v0.19.0

chore: remove BoltDB support

v0.18.3

fix: replace argv[0] when proxying to binaries

This allows executables that find related files relative to their
binary, such as Python, to work.

v0.18.2

fix: missing hermit sha

v0.18.1

Update docs for `hermit update`

Update docs for `hermit update` to include information on hermit updating itself.

Signed-off-by: Julia Ogris <[email protected]>

v0.18.0

fix: don't use metadata dir for legacy BoltDB

v0.17.0

fix: dao: read-through to BBolt if we don't have a FS entry

v0.16.1

fix: only sync packages if forced or update frequency is hit

I noticed that the check is occurring even on search, eg.

    🐚 ~/Development/orc $ hermit search cashcache
    info:cashkite-conventional-commits@stable: No updated required
    info:go@latest: No updated required
    cashcache (@0, @0.0, @latest, 0.0.18, 0.0.21, 0.0.23, 0.0.25, 0.0.27, 0.0.28, 0.0.29, 0.0.30, 0.0.31)
      cashcache is CI cache to improve build times

v0.16.0

feat: sync channels on "hermit update"

This can be used eg. in CI to force updates to the latest of all
dynamically versioned packages.