What changed between 0.2.1 and 0.2.2
From doze-modules history- 0.2.24 JulNo notes for this release.
Same plugin protocol (1) and the same engines (Temporal CLI 1) throughout, so the upgrade needs no change to doze.hcl.
Durable workflow engine (local dev server)
doze/temporal$ doze add temporal0.2.1 sets no oldest doze, so it runs on every doze (0.1.0 and up).
Same plugin protocol (1) and the same engines (Temporal CLI 1) throughout, so the upgrade needs no change to doze.hcl.
Projects pinned to 0.2.1 keep using it until someone runs doze modules upgrade. Nothing moves on its own: not doze up, not time, not a new release.
$ doze modules upgrade temporalNo notes for this release.
| Platform | File (downloads from GitHub) | SHA-256 | Signature (ed25519) |
|---|---|---|---|
| macOS arm64 aarch64-apple-darwin | temporal-plugin-0.2.1-aarch64-apple-darwin.tar.gz | 304b2ea0e81a5732689fb5266030d62b5832825daaba8fdcb6de7edc63a2f57f | K1maQidO…n4BA== |
| Linux arm64 aarch64-unknown-linux-gnu | temporal-plugin-0.2.1-aarch64-unknown-linux-gnu.tar.gz | f2c2fdc362092dad3267e0ac0c2fbd66ee4d2786dcb2f3d0436f79d7223fab11 | 0t+t2MIK…FMBA== |
| Linux x86_64 x86_64-unknown-linux-gnu | temporal-plugin-0.2.1-x86_64-unknown-linux-gnu.tar.gz | 2aa60dda107a49c23c5a81e6929a31b31b84fc53bcd4b69e10d5c562b37ab6ab | IkkC6DRX…rVDg== |
Every file is under https://github.com/doze-dev/doze-modules/releases/download/temporal/. Intel Macs and Windows have no build; WSL2 uses the Linux x86_64 file.
The index is signed as a whole, and each archive is signed. doze checks both before anything runs, and refuses a module whose checksum or signature doesn't match.
Nu5y8mbj…Wjw= ei/e75q9…Aw== doze (oldest doze) field sits beside the signed part today. new The design moves it inside.[planned: doze modules verify] Today doze runs these checks itself on every download. The same checks by hand, for macOS arm64. Needs OpenSSL 3: the openssl that ships with macOS has no ed25519 (brew install openssl@3).
# 1. download and hash; compare with the table above $ curl -LO https://github.com/doze-dev/doze-modules/releases/download/temporal/temporal-plugin-0.2.1-aarch64-apple-darwin.tar.gz $ shasum -a 256 temporal-plugin-0.2.1-aarch64-apple-darwin.tar.gz 304b2ea0e81a5732689fb5266030d62b5832825daaba8fdcb6de7edc63a2f57f temporal-plugin-0.2.1-aarch64-apple-darwin.tar.gz # 2. the signature is over that hex string, with doze's public key $ printf %s 304b2ea0e81a5732689fb5266030d62b5832825daaba8fdcb6de7edc63a2f57f > digest.txt $ echo 'K1maQidOKHCg/QDTWdL0oXnnX/0EIh/ETVJdDMXtzm6VvMTuyLi1ZlTjj7BqKJyAffBpfvJu47o1/z8DJDn4BA==' | base64 -d > sig.bin $ (printf '\x30\x2a\x30\x05\x06\x03\x2b\x65\x70\x03\x21\x00'; echo 'Nu5y8mbjYv7XEtNFBXwPVl+C8SBteVApIROefBwGWjw=' | base64 -d) > doze-key.der $ openssl pkeyutl -verify -pubin -keyform DER -inkey doze-key.der -rawin -in digest.txt -sigfile sig.bin Signature Verified Successfully
A project pinned to 0.2.1 carries this entry. doze modules upgrade replaces it whole: release, engines and checksums move together in one reviewable diff. Every platform's checksum goes in, so a teammate on Linux verifies against the same pin you made on a Mac. Pinned and cached means no network at all.
The engine itself is pinned separately, under engines:. Engine versions
modules:
doze/temporal:
version: 0.2.1
protocol: 1
engines:
- "1"
hashes:
aarch64-apple-darwin: sha256:304b2ea0e81a5732689fb5266030d62b5832825daaba8fdcb6de7edc63a2f57f
aarch64-unknown-linux-gnu: sha256:f2c2fdc362092dad3267e0ac0c2fbd66ee4d2786dcb2f3d0436f79d7223fab11
x86_64-unknown-linux-gnu: sha256:2aa60dda107a49c23c5a81e6929a31b31b84fc53bcd4b69e10d5c562b37ab6ab
# no doze: line; 0.2.1 sets no oldest doze