| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| checksums.txt | 2025-10-24 | 908 Bytes | |
| pocketbase_0.31.0_windows_arm64.zip | 2025-10-24 | 11.8 MB | |
| pocketbase_0.31.0_darwin_amd64.zip | 2025-10-24 | 12.7 MB | |
| pocketbase_0.31.0_darwin_arm64.zip | 2025-10-24 | 12.1 MB | |
| pocketbase_0.31.0_linux_arm64.zip | 2025-10-24 | 11.7 MB | |
| pocketbase_0.31.0_windows_amd64.zip | 2025-10-24 | 12.9 MB | |
| pocketbase_0.31.0_linux_amd64.zip | 2025-10-24 | 12.6 MB | |
| pocketbase_0.31.0_linux_armv7.zip | 2025-10-24 | 12.0 MB | |
| pocketbase_0.31.0_linux_ppc64le.zip | 2025-10-24 | 11.8 MB | |
| pocketbase_0.31.0_linux_s390x.zip | 2025-10-24 | 12.3 MB | |
| README.md | 2025-10-23 | 1.9 kB | |
| v0.31.0 Release source code.tar.gz | 2025-10-23 | 4.4 MB | |
| v0.31.0 Release source code.zip | 2025-10-23 | 5.0 MB | |
| Totals: 13 Items | 119.4 MB | 6 | |
To update the prebuilt executable you can run
./pocketbase update.
-
Display presentable multiple
relationfields (#7260). -
Support Ed25519 in the optional OIDC
id_tokensignature validation (#7252; thanks @shynome). -
Added
ApiScenario.DisableTestAppCleanupoptional field to skip the auto test app cleanup and leave it up to the developers to do the cleanup manually (#7267). -
Added
FileDownloadRequestEvent.ThumbErrorfield that is populated in case of a thumb generation failure (e.g. unsupported format, timing out, etc.), allowing developers to reject the thumb fallback and/or supply their own custom thumb generation (#7268). -
⚠️ Disallow client-side filtering and sorting of relations where the collection of the last targeted relation field has superusers-only List/Search API rule to further minimize the risk of eventual side-channel attack. This should be a non-breaking change for most users, but if you want the old behavior please open a Q&A discussion with details about your use case to evaluate making it configurable. Note also that as mentioned in the "Security and performance" section of #4417 and #5863, the easiest and recommended solution to protect security sensitive fields (tokens, codes, passwords, etc.) is to mark them as "Hidden" (aka. make them non-API filterable). A better out of the box handling will be available with the planned fields internals refactoring together with the already started UI rewrite and plugins support.
-
Regenerated JSVM types and updated npm and Go deps.