ClearBootstrap is the Important line in PocketBase 0.40.4

So PocketBase Releases put v0.40.4 on the feed, and we flagged it Important as a deprecation. Recency wants the deadlock story. Fine. The note opens on a fixed migration deadlock when a logs db write runs while a migration is still executing (issue 7836), plus a reminder you can update the prebuilt executable with ./pocketbase update. That is what people screenshot.

The line that matters, to the best of my understanding, is further down. app.ResetBootstrapState() was soft-deprecated in favor of app.ClearBootstrap(). Soft-deprecated, not yanked, which is kind of how these renames sneak into partner tickets. Same note ships a new app.OnClearBootstrap() hook so you can clear custom OnBootstrap resources when the app uses a non-standard initialization (for example it does not call Start(), or it intentionally skips the OnTerminate hook). Kind of easy to miss if you stop at the deadlock headline.

I keep almost filing PocketBase patch tags under "backend bump, ignore." Kind of the wrong habit when a customer rebuilt on a custom bootstrap path and their AE asks why ResetBootstrapState started smelling deprecated overnight. Let's say the talking point is not "0.40.4 fixed a deadlock." It is the bootstrap clear API renamed, then check whether you need OnClearBootstrap if you own a weird init path. golang.org/x dependencies got bumped too. That is real, and still secondary to the rename if you sell into teams that fork the bootstrap lifecycle.

We pull it into a uniform entry shape at /sources/pocketbase-releases. Same JSON as everything else. The talking point is ClearBootstrap replaces ResetBootstrapState, then OnClearBootstrap for non-standard init, then yes the deadlock fix is worth a sentence. Recency still wants the deadlock. Recency is not the deprecation line.