Слияние кода завершено, страница обновится автоматически
⚠️ Moved the Create and Manage API rule checks out of the OnRecordCreateRequest hook finalizer, aka. now all CRUD API rules are checked BEFORE triggering their corresponding *Request hook.
This was done to minimize the confusion regarding the firing order of the request operations, making it more predictable and consistent with the other record List/View/Update/Delete request actions.
It could be a minor breaking change if you are relying on the old behavior and have a Go tests.ApiScenario that is testing a Create API rule failure and expect OnRecordCreateRequest to be fired. In that case for example you may have to update your test scenario like:
tests.ApiScenario{
Name: "Example test that checks a Create API rule failure"
Method: http.MethodPost,
URL: "/api/collections/example/records",
...
// old:
ExpectedEvents: map[string]int{
"*": 0,
"OnRecordCreateRequest": 1,
},
// new:
ExpectedEvents: map[string]int{"*": 0},
}
If you are having difficulties adjusting your code, feel free to open a Q&A discussion with the failing/problematic code sample.
Added new geoPoint field for storing {"lon":x,"lat":y} geographic coordinates.
In addition, a new geoDistance(lonA, lotA, lonB, lotB) function was also implemented that could be used to apply an API rule or filter constraint based on the distance (in km) between 2 geo points.
Updated the select field UI to accommodate better larger lists and RTL languages (#4674).
Updated the mail attachments auto MIME type detection to use gabriel-vasile/mimetype for consistency and broader sniffing signatures support.
Forced text/javascript Content-Type when serving .js/.mjs collection uploaded files with the /api/files/... endpoint (#6597).
Added second optional JSVM DateTime constructor argument for specifying a default timezone as TZ identifier when parsing the date string as alternative to a fixed offset in order to better handle daylight saving time nuances (#6688):
// the same as with CET offset: new DateTime("2025-10-26 03:00:00 +01:00")
new DateTime("2025-10-26 03:00:00", "Europe/Amsterdam") // 2025-10-26 02:00:00.000Z
// the same as with CEST offset: new DateTime("2025-10-26 01:00:00 +02:00")
new DateTime("2025-10-26 01:00:00", "Europe/Amsterdam") // 2025-10-25 23:00:00.000Z
Soft-deprecated the $http.send's result.raw field in favor of result.body that contains the response body as plain bytes slice to avoid the discrepancies between Go and the JSVM when casting binary data to string.
Updated modernc.org/sqlite to 1.37.0.
Other minor improvements (removed the superuser fields from the auth record create/update body examples, allowed programmatically updating the auth record password from the create/update hooks, fixed collections import error response, etc.).
Allow OIDC email_verified to be int or boolean string since some OIDC providers like AWS Cognito has non-standard userinfo response (#6657).
Updated modernc.org/sqlite to 1.36.3.
Fixed RecordErrorEvent.Error and CollectionErrorEvent.Error sync with ModelErrorEvent.Error (#6639).
Fixed logs details copy to clipboard action.
Updated modernc.org/sqlite to 1.36.2.
golang-jwt/jwt dependency because it comes with a minor security fix.io.EOF error when reading files since currently io.ReadAll doesn't check for wrapped errors (#6600).⚠️ Replaced aws-sdk-go-v2 and gocloud.dev/blob with custom lighter implementation (#6562).
As a side-effect of the dependency removal, the binary size has been reduced with ~10MB and builds ~30% faster.
Although the change is expected to be backward-compatible, I'd recommend to test first locally the new version with your S3 provider (if you use S3 for files storage and backups).
⚠️ Prioritized the user submitted non-empty createData.email (it will be unverified) when creating the PocketBase user during the first OAuth2 auth.
Load the request info context during password/OAuth2/OTP authentication (#6402).
This could be useful in case you want to target the auth method as part of the MFA and Auth API rules.
For example, to disable MFA for the OAuth2 auth could be expressed as @request.context != "oauth2" MFA rule.
Added store.Store.SetFunc(key, func(old T) new T) to set/update a store value with the return result of the callback in a concurrent safe manner.
Added subscription.Message.WriteSSE(w, id) for writing an SSE formatted message into the provided writer interface (used mostly to assist with the unit testing).
Added $os.stat(file) JSVM helper (#6407).
Added log warning for async marked JSVM handlers and resolve when possible the returned Promise as fallback (#6476).
Allowed calling cronAdd, cronRemove from inside other JSVM handlers (#6481).
Bumped the default request read and write timeouts to 5mins (old 3mins) to accommodate slower internet connections and larger file uploads/downloads.
If you want to change them you can modify the OnServe hook's ServeEvent.ReadTimeout/WriteTimeout fields as shown in #6550.
Normalized the @request.auth.* and @request.body.* back relations resolver to always return null when the relation field is pointing to a different collection (#6590).
Other minor improvements (fixed query dev log nested parameters output, reintroduced DynamicModel object/array props reflect types caching, updated Go and npm deps, etc.)
DynamicModel object/array props reflect type caching (#6563).id_token timestamp claims check to account for clock-skew (#6529).
It can be further customized if needed with the PB_ID_TOKEN_LEEWAY env variable (the value must be in seconds, e.g. "PB_ID_TOKEN_LEEWAY=60" for 1 minute).@request.body.jsonObjOrArr.* values extraction (#6493).Restore the missing meta.isNew field of the OAuth2 success response (#6490).
Updated npm dependencies.
Set the current working directory as a default goja script path when executing inline JS strings to allow require(m) traversing parent node_modules directories.
Updated modernc.org/sqlite and modernc.org/libc dependencies.
Downgraded aws-sdk-go-v2 to the version before the default data integrity checks because there have been reports for non-AWS S3 providers in addition to Backblaze (IDrive, R2) that no longer or partially work with the latest AWS SDK changes.
While we try to enforce when_required by default, it is not enough to disable the new AWS SDK integrity checks entirely and some providers will require additional manual adjustments to make them compatible with the latest AWS SDK (e.g. removing the x-aws-checksum-* headers, unsetting the checksums calculation or reinstantiating the old MD5 checksums for some of the required operations, etc.) which as a result leads to a configuration mess that I'm not sure it would be a good idea to introduce.
This unfornuatelly is not a PocketBase or Go specific issue and the official AWS SDKs for other languages are in the same situation (even the latest aws-cli).
For those of you that extend PocketBase with Go: if your S3 vendor doesn't support the AWS Data integrity checks and you are updating with go get -u, then make sure that the aws-sdk-go-v2 dependencies in your go.mod are the same as in the repo:
// go.mod
github.com/aws/aws-sdk-go-v2 v1.36.1
github.com/aws/aws-sdk-go-v2/config v1.28.10
github.com/aws/aws-sdk-go-v2/credentials v1.17.51
github.com/aws/aws-sdk-go-v2/feature/s3/manager v1.17.48
github.com/aws/aws-sdk-go-v2/service/s3 v1.72.2
// after that run
go clean -modcache && go mod tidy
The versions pinning is temporary until the non-AWS S3 vendors patch their implementation or until I manage to find time to remove/replace the aws-sdk-go-v2 dependency (I'll consider prioritizing it for the v0.26 or v0.27 release).
aws-sdk-go-v2 checksum headers (#6440).RecordProxy-ies and added basic realtime record resolve automated tests (#6433).Fixed the batch API Preview success sample response.
Bumped GitHub action min Go version to 1.23.6 as it comes with a minor security fix for the ppc64le build.
⚠️ Upgraded Google OAuth2 auth, token and userinfo endpoints to their latest versions. For users that don't do anything custom with the Google OAuth2 data or the OAuth2 auth URL, this should be a non-breaking change. The exceptions that I could find are:
/v3/userinfo auth response changes:
meta.rawUser.id => meta.rawUser.sub
meta.rawUser.verified_email => meta.rawUser.email_verified
/v2/auth query parameters changes:
If you are specifying custom approval_prompt=force query parameter for the OAuth2 auth URL, you'll have to replace it with prompt=consent.Added Trakt OAuth2 provider (#6338; thanks @aidan-)
Added support for case-insensitive password auth based on the related UNIQUE index field collation (#6337).
Enforced when_required for the new AWS SDK request and response checksum validations to allow other non-AWS vendors to catch up with new AWS SDK changes (see #6313 and aws/aws-sdk-go-v2#2960).
You can set the environment variables AWS_REQUEST_CHECKSUM_CALCULATION and AWS_RESPONSE_CHECKSUM_VALIDATION to when_supported if your S3 vendor supports the new default integrity protections.
Soft-deprecated Record.GetUploadedFiles in favor of Record.GetUnsavedFiles to minimize the ambiguities what the method do (#6269).
Replaced archived github.com/AlecAivazis/survey dependency with a simpler osutils.YesNoPrompt(message, fallback) helper.
Upgraded to golang-jwt/jwt/v5.
Added JSVM new Timezone(name) binding for constructing time.Location value (#6219).
Added inflector.Camelize(str) and inflector.Singularize(str) helper methods.
Use the non-transactional app instance during the realtime records delete access checks to ensure that cascade deleted records with API rules relying on the parent will be resolved.
Other minor improvements (replaced all bool exists db scans with int for broader drivers compatibility, updated API Preview sample error responses, updated UI dependencies, etc.)
Fixed fields extraction for view query with nested comments (#6309).
Bumped GitHub action min Go version to 1.23.5 as it comes with some minor security fixes.
Fixed incorrectly reported unique validator error for fields starting with name of another field (#6281; thanks @svobol13).
Reload the created/edited records data in the RecordsPicker UI.
Updated Go dependencies.
relation fields in a single related collection (#6229).Added missing time macros in the UI autocomplete.
Fixed JSVM types for structs and functions with multiple generic parameters.
⚠️ Removed the "dry submit" when executing the collections Create API rule
(you can find more details why this change was introduced and how it could affect your app in https://github.com/pocketbase/pocketbase/discussions/6073).
For most users it should be non-breaking change, BUT if you have Create API rules that uses self-references or view counters you may have to adjust them manually.
With this change the "multi-match" operators are also normalized in case the targeted collection doesn't have any records
(or in other words, @collection.example.someField != "test" will result to true if example collection has no records because it satisfies the condition that all available "example" records mustn't have someField equal to "test").
As a side-effect of all of the above minor changes, the record create API performance has been also improved ~4x times in high concurrent scenarios (500 concurrent clients inserting total of 50k records - old (58.409064001s) vs new (13.580098262s)).
⚠️ Changed the type definition of store.Store[T any] to store.Store[K comparable, T any] to allow support for custom store key types.
For most users it should be non-breaking change, BUT if you are calling store.New[any](nil) instances you'll have to specify the store key type, aka. store.New[string, any](nil).
Added @yesterday and @tomorrow datetime filter macros.
Added :lower filter modifier (e.g. title:lower = "lorem").
Added mailer.Message.InlineAttachments field for attaching inline files to an email (aka. cid links).
Added cache for the JSVM arrayOf(m), DynamicModel, etc. dynamic reflect created types.
Added auth collection select for the settings "Send test email" popup (#6166).
Added record.SetRandomPassword() to simplify random password generation usually used in the OAuth2 or OTP record creation flows.
The generated ~30 chars random password is assigned directly as bcrypt hash and ignores the password field plain value validators like min/max length or regex pattern.
Added option to list and trigger the registered app level cron jobs via the Web API and UI.
Added extra validators for the collection field int64 options (e.g. FileField.MaxSize) restricting them to the max safe JSON number (2^53-1).
Added option to unset/overwrite the default PocketBase superuser installer using ServeEvent.InstallerFunc.
Added app.FindCachedCollectionReferences(collection, excludeIds) to speedup records cascade delete almost twice for projects with many collections.
Added tests.NewTestAppWithConfig(config) helper if you need more control over the test configurations like IsDev, the number of allowed connections, etc.
Invalidate all record tokens when the auth record email is changed programmatically or by a superuser (#5964).
Eagerly interrupt waiting for the email alert send in case it takes longer than 15s.
Normalized the hidden fields filter checks and allow targetting hidden fields in the List API rule.
Fixed "Unique identify fields" input not refreshing on unique indexes change (#6184).
Added warning logs in case of mismatched modernc.org/sqlite and modernc.org/libc versions (#6136).
Skipped the default body size limit middleware for the backup upload endpoint (#6152).
golang.org/x/net to 0.33.0 to fix CVE-2024-45338.
PocketBase uses the vulnerable functions primarily for the auto html->text mail generation, but most applications shouldn't be affected unless you are manually embedding unrestricted user provided value in your mail templates.
Renew the superuser file token cache when clicking on the thumb preview or download link (#6137).
Upgraded modernc.org/sqlite to 1.34.3 to fix "disk io" error on arm64 systems.
If you are extending PocketBase with Go and upgrading with go get -u make sure to manually set in your go.mod the modernc.org/libc indirect dependency to v1.55.3, aka. the exact same version the driver is using.
strconv.Itoa with strconv.FormatInt to avoid the int64->int conversion overflow on 32-bit platforms (#6132).Fixed Model->Record and Model->Collection hook events sync for nested and/or inner-hook transactions (#6122).
Other minor improvements (updated Go and npm deps, added extra escaping for the default mail record params in case the emails are stored as html files, fixed code comment typos, etc.).
Fixed $filesystem.fileFromURL documentation and generated type (#6058).
Fixed X-Forwarded-For header typo in the suggested UI "Common trusted proxy" headers (#6063).
Updated the text field max length validator error message to make it more clear (#6066).
Other minor fixes (updated Go deps, skipped unnecessary validator check when the default primary key pattern is used, updated JSVM types, etc.).
Fixed UI logs search not properly accounting for the "Include requests by superusers" toggle when multiple search expressions are used.
Fixed text field max validation error message (#6053).
Other minor fixes (comment typos, JSVM types update).
Updated Go deps and the min Go release GitHub action version to 1.23.4.
Fixed autodate fields not refreshing when calling Save multiple times on the same Record instance (#6000).
Added more descriptive test OTP id and failure log message (#5982).
Moved the default UI CSP from meta tag to response header (#5995).
Updated Go and npm dependencies.
Fixed Gzip middleware not applying when serving static files.
Fixed Record.Fresh()/Record.Clone() methods not properly cloning autodate fields (#5973).
Fixed RecordQuery() custom struct scanning (#5958).
Fixed --dev log query print formatting.
Added support for passing more than one id in the Hook.Unbind method for consistency with the router.
Added collection rules change list in the confirmation popup (to avoid getting anoying during development, the rules confirmation currently is enabled only when using https).
Added RequestEvent.Blob(status, contentType, bytes) response write helper (#5940).
Added more descriptive error messages.
[!NOTE] You don't have to upgrade to PocketBase v0.23.0 if you are not planning further developing your existing app and/or are satisfied with the v0.22.x features set. There are no identified critical issues with PocketBase v0.22.x yet and in the case of critical bugs and security vulnerabilities, the fixes will be backported for at least until Q1 of 2025 (if not longer).
If you don't plan upgrading make sure to pin the SDKs version to their latest PocketBase v0.22.x compatible:
- JS SDK:
<0.22.0- Dart SDK:
<0.19.0
[!CAUTION] This release introduces many Go/JSVM and Web APIs breaking changes!
Existing
pb_datawill be automatically upgraded with the start of the new executable, but custom Go or JSVM (pb_hooks,pb_migrations) and JS/Dart SDK code will have to be migrated manually. Please refer to the below upgrade guides:If you had already switched to some of the earlier
<v0.23.0-rc14versions and have generated a full collections snapshot migration (aka../pocketbase migrate collections), then you may have to regenerate the migration file to ensure that it includes the latest changes.
PocketBase v0.23.0 is a major refactor of the internals with the overall goal of making PocketBase an easier to use Go framework. There are a lot of changes but to highlight some of the most notable ones:
echo with a new router built on top of the Go 1.22 net/http mux enhancements.daos packages in core.App to simplify the DB operations (the models package structs are also migrated in core).DBConnect function as part of the app configuration to allow different database/sql SQLite drivers (turso/libsql, sqlcipher, etc.) and custom builds.
Note that we no longer loads the mattn/go-sqlite3 driver by default when building with CGO_ENABLED=1 to avoid multiple definition linker errors in case different CGO SQLite drivers or builds are used. You can find an example how to enable it back if you want to in the new documentation.
Record model improvements (support for get/set modifiers, simplfied file upload by treating the file(s) as regular field value like record.Set("document", file), etc.).id, email, password, etc.)._superusers auth records.instagram2 to prevent conflicts with existing linked users.
id_token payload for the cases when the provider doesn't have a dedicated user info endpoint.Presentable view, slightly different collection options organization, zoom/pan for the logs chart, etc.)New POST /api/batch endpoint.
New GET /api/collections/meta/scaffolds endpoint.
New DELETE /api/collections/{collection}/truncate endpoint.
New POST /api/collections/{collection}/request-otp endpoint.
New POST /api/collections/{collection}/auth-with-otp endpoint.
New POST /api/collections/{collection}/impersonate/{id} endpoint.
⚠️ If you are constructing requests to /api/* routes manually remove the trailing slash (there is no longer trailing slash removal middleware registered by default).
⚠️ Removed /api/admins/* endpoints because admins are converted to _superusers auth collection records.
⚠️ Previously when uploading new files to a multiple file field, new files were automatically appended to the existing field values.
This behaviour has changed with v0.23+ and for consistency with the other multi-valued fields when uploading new files they will replace the old ones. If you want to prepend or append new files to an existing multiple file field value you can use the + prefix or suffix:
"documents": [file1, file2] // => [file1_name, file2_name]
"+documents": [file1, file2] // => [file1_name, file2_name, old1_name, old2_name]
"documents+": [file1, file2] // => [old1_name, old2_name, file1_name, file2_name]
⚠️ Removed GET /records/{id}/external-auths and DELETE /records/{id}/external-auths/{provider} endpoints because this is now handled by sending list and delete requests to the _externalAuths collection.
⚠️ Changes to the app settings model fields and response (+new options such as trustedProxy, rateLimits, batch, etc.). The app settings Web APIs are mostly used by the Dashboard UI and rarely by the end users, but if you want to check all settings changes please refer to the Settings Go struct.
⚠️ New flatten Collection model and fields structure. The Collection model Web APIs are mostly used by the Dashboard UI and rarely by the end users, but if you want to check all changes please refer to the Collection Go struct.
⚠️ The top level error response code key was renamed to status for consistency with the Go APIs.
The error field key remains code:
{
"status": 400, // <-- old: "code"
"message": "Failed to create record.",
"data": {
"title": {
"code": "validation_required",
"message": "Missing required value."
}
}
}
⚠️ New fields in the GET /api/collections/{collection}/auth-methods response.
The old authProviders, usernamePassword, emailPassword fields are still returned in the response but are considered deprecated and will be removed in the future.
{
"mfa": {
"duration": 100,
"enabled": true
},
"otp": {
"duration": 0,
"enabled": false
},
"password": {
"enabled": true,
"identityFields": ["email", "username"]
},
"oauth2": {
"enabled": true,
"providers": [{"name": "gitlab", ...}, {"name": "google", ...}]
},
// old fields...
}
⚠️ Soft-deprecated the OAuth2 auth success meta.avatarUrl field in favour of meta.avatarURL.
Вы можете оставить комментарий после Вход в систему
Неприемлемый контент может быть отображен здесь и не будет показан на странице. Вы можете проверить и изменить его с помощью соответствующей функции редактирования.
Если вы подтверждаете, что содержание не содержит непристойной лексики/перенаправления на рекламу/насилия/вульгарной порнографии/нарушений/пиратства/ложного/незначительного или незаконного контента, связанного с национальными законами и предписаниями, вы можете нажать «Отправить» для подачи апелляции, и мы обработаем ее как можно скорее.
Опубликовать ( 0 )