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.

FerretDB

OfficialSigned

MongoDB-compatible database (FerretDB v2 over Postgres)

doze/ferret
$ doze add ferret
Newest
0.2.3 · 2 Nov 2026
Needs
any doze
Runs
FerretDB 2
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. ferret 0.2.1 – 0.2.3Currentany dozeJul–Nov 2026. No 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 dozeProtocolFerretDBPlatformsNotes
0.23 in the index · newest 0.2.3
0.2.32 Nov 2026Currentany doze12macarmx86
0.2.23 Jul 2026Supersededany doze12macarmx86The readiness check connects as -U postgres, not your OS user.
0.2.12 Jul 2026Supersededany doze12macarmx86

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.

Not in the index

GitHub has older ferret builds than the registry lists. doze only resolves what the signed index names, so these can't land in a doze.lock.

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
ferret    doze/ferret    0.2.2   0.2.3     upgrade available

1 module upgrade(s) available — run doze modules upgrade
2. Move the pin
$ doze modules upgrade ferret
ENGINE    SOURCE         PINNED  SELECTED  STATUS
ferret    doze/ferret    0.2.2   0.2.3     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/ferret:
-        version: 0.2.2
+        version: 0.2.3
         protocol: 1
         engines:
             - "2"
         hashes:
-            aarch64-apple-darwin: sha256:7bdde3bfd9c41c01c9b14884e20432486fe82ab5c8e474ca19832cdd986753fb
-            aarch64-unknown-linux-gnu: sha256:e962983b1006a0a3469ef1b7b0c11610d07be6c82de0ef0babe0885f6318252b
-            x86_64-unknown-linux-gnu: sha256:53f98d691f348b3cafe59452083b905196a686521ee0ff0b2ecda44839bd1bcd
+            aarch64-apple-darwin: sha256:c658434a1d781d2f3b81d8fe114cad6ac1943a324b5bd2b09e63ec8544c9d37c
+            aarch64-unknown-linux-gnu: sha256:d7c189497583a23859b74d6eefdddd2a231dfff459ff874b03fb65a47dabcb1e
+            x86_64-unknown-linux-gnu: sha256:40de4c1878177a21ad67a682387b1d142bceaa3eb47c9d83f98e1d4a65cfb363