⚠️ Breaking Change
Impact Score: 7/10
PocketBase: v0.3.0 Release
Source available — automated, not human-reviewed
Component: pocketbase · Channel: stable. Automated analysis, not a compatibility certification. How this works.
Analysis updated: 2026-11-01.
Breaking-change evidence from the source
:warning: This release introduce a small breaking change related to `null` handling (read below for more info).
This is a minor breaking change if you previously relied on the `null` value**. Here is a full list with all the supported field values:
⚡ Executive Summary (TL;DR)
PocketBase v0.3.0. Source highlight: :warning: This release introduce a small breaking change related to `null` handling (read below for more info).
Who Does This Impact? (Role-Based Analysis)
💻 Software Engineers & Devs
Check the source notes against the package and APIs you use before upgrading.
📊 Product & Engineering Leads
Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.
⚙️ DevOps & Security
Verify the target version, runtime requirements and rollback procedure in the official documentation.
⚠️ Breaking Changes & Deprecations (2)
- :warning: This release introduce a small breaking change related to `null` handling (read below for more info).
- This is a minor breaking change if you previously relied on the `null` value**. Here is a full list with all the supported field values:
✨ New Features & Capabilities (2)
- added better frontend handling when duplicated or invalid field names are typed
- added the app name in the document title
⚡ Performance & Enhancements (2)
- Improved collection schema updates - now is allowed to rename/switch existing field names in the same request.
- Admin UI improvements:
🔧 Bug Fixes & Patches (1)
- fixed the repeated initial records list load
📄 View Raw Release Notes (Original Developer Log)
## Changes
> :warning: This release introduce a small breaking change related to `null` handling (read below for more info).
> It is recommended to backup your `pb_data` directory before upgrading/replacing the binary.
- All field values are now normalized and will return only a non-null value (only exception is the JSON field) [#122].
**This is a minor breaking change if you previously relied on the `null` value**. Here is a full list with all the supported field values:
| Field | Supported value |
|:--------------------|:-----------------------------------------------|
| Text | `""`, `"test"` |
| Number | `0`, `-1`, `1`, `1.5` |
| Bool | `false`, `true` |
| Email | `""`, `"[email protected]"` |
| Url | `""`, `"https://example.com"` |
| Date | `""`, `"2022-01-01 00:00:00.000"` |
| Select (single) | `""`, `"optionA"` |
| Select (multiple) | `[]`, `["optionA", "optionB"]` |
| File (single) | `""`, `"12i...ZjL.png"` |
| File (multiple) | `[]`, `["12i...ZjL.png", "34i...ZjL.txt"]` |
| Relation (single) | `""`, `"74kmig0HEyR7uuD"` |
| Relation (multiple) | `[]`, `["74kmig0HEyR7uuD", "FtHAW9feB5rze7D"]` |
| User (single) | `""`, `"74kmig0HEyR7uuD"` |
| User (multiple) | `[]`, `["74kmig0HEyR7uuD", "FtHAW9feB5rze7D"]` |
| \* _JSON_ | `any json value` |
Sending `null` in the request data is OK, since it will be casted to the respective zero-value before processing.
- Improved collection schema updates - now is allowed to rename/switch existing field names in the same request.
- Delete the storage files of cascade deleted Records [#151].
- Admin UI improvements:
- reduced the spacing in the collections settings panel to make it more comfortable editing API rules and fields
- updated the field accordion component styles
- added better frontend handling when duplicated or invalid field names are typed
- on record create/update the confirmation modal will no longer show if there are no changes
- added the app name in the document title
- fixed the repeated initial records list load