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 AWS

OfficialSigned

The whole local AWS as ONE service — with its web console.

doze/aws
$ doze add aws
Newest
0.2.0 · [date]
Needs
doze 0.2.0 or newer
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 up to 0.1.1 · doze 0.2.0 from 0.2.0

  1. aws 0.1.0 – 0.1.1any dozeJul 2026. No oldest-doze field, so they run on every doze, 0.1.0 and up.
  2. aws 0.2.0Currentdoze 0.2.0 or newerThe index carries doze: 0.2.0 for it.

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 dozeProtocolEnginesPlatformsNotes
0.21 in the index · newest 0.2.0
0.2.0[date]Currentdoze 0.2.01—macarmx86
0.12 in the index · newest 0.1.1
0.1.118 Jul 2026Supersededany doze1—macarmx86
0.1.018 Jul 2026Supersededany doze1—macarmx86

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
aws       doze/aws       0.1.1   0.2.0     upgrade available

1 module upgrade(s) available — run doze modules upgrade
2. Move the pin
$ doze modules upgrade aws
ENGINE    SOURCE         PINNED  SELECTED  STATUS
aws       doze/aws       0.1.1   0.2.0     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.

3. The doze.lock diff to commit
 modules:
     doze/aws:
-        version: 0.1.1
+        version: 0.2.0
         protocol: 1
         hashes:
-            aarch64-apple-darwin: sha256:10edd75a23bb969559bb65ea4191f92edfcad1cd52e2d506c48af9d538ccb9e3
-            aarch64-unknown-linux-gnu: sha256:9a986d2836ee746bbc370539978bfd37c34aa8b7650277228f9f240f66c1f1b7
-            x86_64-unknown-linux-gnu: sha256:dd0fd25000e0cf5514650b53f67acc3821b45c8140dc3b3caa1921631c93d02d
+            aarch64-apple-darwin: sha256:3cad5bd89b6b89ac8136f01a885415f557d3d8835e883c26a45f59fafcdfa8b8
+            aarch64-unknown-linux-gnu: sha256:161e19963120b98ce77bbef48aa2392bd1e518b0220e09def2bce1c6860c989c
+            x86_64-unknown-linux-gnu: sha256:2dbbf9bfb13c304d5ef46ad93bf7043310e03b7f427a6fe61fc105bbed3476a1
+        doze: 0.2.0