dozeGitHubGet doze
Registry
Check against your doze

Which doze do you run?

doze 0.1.1newest · 2 Jul 2026doze 0.1.02 Jul 2026Stop checkingKept in this browser only. Nothing is sent anywhere.

doze Kafka

OfficialSigned

Single-node Kafka-protocol broker, no JVM.

doze/kafka
$ doze add kafka
Newest
0.1.2 · [date]
Needs
any doze
Runs
runs itself
Platforms
macOS arm64 · Linux arm64 · Linux x86_64
Licence
Apache-2.0
Source
on GitHub

Versions

Three releases resolve, newest first. Nothing is ever taken down: a project pinned to any of them keeps working, and doze modules upgrade is the only thing that moves a pin.

The signed index.yaml
Oldest doze, by release

Any doze, every release

  1. kafka 0.1.0 – 0.1.2Currentany dozeNo oldest-doze field, so they run on every doze, 0.1.0 and up.

The release tool writes the field from the SDK the module was built with, always as three numbers. A doze older than a release's minimum skips it and takes the newest release that fits.

doze 0.1.1 can't read a release's minimum doze. Update doze first, with brew upgrade doze, then run doze modules upgrade.

All releases

Platforms:mac macOS arm64 arm Linux arm64 x86 Linux x86_64
VersionReleasedStatusNeeds dozeProtocolKafka protocolPlatformsNotes
0.13 in the index · newest 0.1.2
0.1.2[date]Currentany doze11234macarmx86
0.1.118 Jul 2026Supersededany doze11234macarmx86
0.1.017 Jul 2026Supersededany doze11234macarmx86

No download counts here: doze sends no telemetry, so nobody, including us, knows how often a release is fetched. Security advisories: none known for any release.

Upgrading a project

A project stays on the release in its doze.lock until you move it. Check first; the upgrade takes the newest release your doze can run, verifies it, and rewrites the pin.

1. See what would move (changes nothing; exits 1 if anything would)
$ doze modules upgrade --check
ENGINE    SOURCE         PINNED  SELECTED  STATUS
kafka     doze/kafka     0.1.1   0.1.2     upgrade available

1 module upgrade(s) available — run doze modules upgrade
2. Move the pin
$ doze modules upgrade kafka
ENGINE    SOURCE         PINNED  SELECTED  STATUS
kafka     doze/kafka     0.1.1   0.1.2     upgraded

doze.lock updated — commit it so the team and CI pick up the same builds

On doze 0.1.1, update doze first: it can't read a release's minimum doze. Engine pins never move with a module upgrade.

3. The doze.lock diff to commit
 modules:
     doze/kafka:
-        version: 0.1.1
+        version: 0.1.2
         protocol: 1
         engines:
             - "1"
             - "2"
             - "3"
             - "4"
         hashes:
-            aarch64-apple-darwin: sha256:c5dfcbf911517ac8718aac8f7f9f94fceb473a4482cad37abf68ec4472c71ed6
-            aarch64-unknown-linux-gnu: sha256:644d99d060ea0878c47f4b8a6dab5ab2bbc6d73462a0fe3576aaec056c33b184
-            x86_64-unknown-linux-gnu: sha256:eaf11bab449e281be6483cf18586502ffef2b4db6c5426db5fbe01ce02cc4640
+            aarch64-apple-darwin: sha256:743008ce131ad35ffd28c870856b752f648f1b88de29e0b928e3efad94ee39f7
+            aarch64-unknown-linux-gnu: sha256:6c0d3bf3d046371a452f6616f6fe7b7dbb7d0a90028ae84715f8f7db43f2f660
+            x86_64-unknown-linux-gnu: sha256:af3ef68b36c546f034c0b13344bfcac5757fd6c9f4d85bce7e672bbd8f32d814