[Snyk] Upgrade pocketbase from 0.20.3 to 0.21.0 #3
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
javascript
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nord-studio/katarogu-old!3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "snyk-upgrade-4e2fc3b249ac310c428b2bf5c40bf0d0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade pocketbase from 0.20.3 to 0.21.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: pocketbase
-
0.21.0 - 2024-01-24
-
-
-
0.20.3 - 2024-01-14
-
from pocketbase GitHub release notes⚠️ This release works only with PocketBase v0.21.0+ due to changes of how the
multipart/form-databody is handled.Properly sent json body with
multipart/form-datarequests.This should fix the edge cases mentioned in the v0.20.3 release.
Gracefully handle OAuth2 redirect error with the
authWithOAuth2()call.Partial and temporary workaround for the auto
application/json->multipart/form-datarequest serialization of ajsonfield when aBlob/Fileis found in the request body (#274).The "fix" is partial because there are still 2 edge cases that are not handled - when a
jsonfield value is empty array (eg.[]) or array of strings (eg.["a","b"]).The reason for this is because the SDK doesn't have information about the field types and doesn't know which field is a
jsonor an arrayableselect,fileorrelation, so it can't serialize it properly on its own asFormDatastring value.If you are having troubles with persisting
jsonvalues as part of amultipart/form-datarequest the easiest fix for now is to manually stringify thejsonfield value:A proper fix for this will be implemented with PocketBase v0.21.0 where we'll have support for a special
@ jsonPayloadmultipart body key, which will allow us to submit mixedmultipart/form-datacontent (kindof similar to themultipart/mixedMIME).Commit messages
Package name: pocketbase
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Pull request closed