🤖 Bump pocketbase from 0.21.2 to 0.25.0 in /frontend

[dependabot]

Bumps pocketbase from 0.21.2 to 0.25.0.

Release notes

Sourced from pocketbase's releases.

v0.25.0 Release

• Added pb.crons service to interact with the cron Web APIs (available with PocketBase v0.24+).

v0.24.0 Release

• Added support for assigning FormData as body to individual batch requests (pocketbase#6145).

v0.23.0 Release

• Added optional pb.realtime.onDisconnect hook function. Note that the realtime client autoreconnect on its own and this hook is useful only for the cases where you want to apply a special behavior on server error or after closing the realtime connection.

v0.22.1 Release

• Fixed old pb.authStore.isAdmin/pb.authStore.isAuthRecord getters and marked them as deprecated in favour of pb.authStore.isSuperuser (#323). Note that with PocketBase v0.23.0 superusers are converted to a system auth collection so you can always simply check the value of pb.authStore.record?.collectionName.

v0.22.0 Release

⚠️ This release introduces some breaking changes and works only with PocketBase v0.23.0+.

• Added support for sending batch/transactional create/updated/delete/upsert requests with the new batch Web APIs.

  const batch = pb.createBatch();
  batch.collection("example1").create({ ... });
  batch.collection("example2").update("RECORD_ID", { ... });
  batch.collection("example3").delete("RECORD_ID");
  batch.collection("example4").upsert({ ... });
  const result = await batch.send();

• Added support for authenticating with OTP (email code):

  const result = await pb.collection("users").requestOTP("test@example.com");
  // ... show a modal for users to check their email and to enter the received code ...
  await pb.collection("users").authWithOTP(result.otpId, "EMAIL_CODE");

  Note that PocketBase v0.23.0 comes also with Multi-factor authentication (MFA) support. When enabled from the dashboard, the first auth attempt will result in 401 response and a mfaId response, that will have to be submitted with the second auth request. For example:

  try {
    await pb.collection("users").authWithPassword("test@example.com", "1234567890");
  } catch (err) {
    const mfaId = err.response?.mfaId;
    if (!mfaId) {
      throw err; // not mfa -> rethrow
    }

... (truncated)

Changelog

Sourced from pocketbase's changelog.

0.25.0

• Added pb.crons service to interact with the cron Web APIs.

0.24.0

• Added support for assigning FormData as body to individual batch requests (pocketbase#6145).

0.23.0

• Added optional pb.realtime.onDisconnect hook function. Note that the realtime client autoreconnect on its own and this hook is useful only for the cases where you want to apply a special behavior on server error or after closing the realtime connection.

0.22.1

• Fixed old pb.authStore.isAdmin/pb.authStore.isAuthRecord and marked them as deprecated in favour of pb.authStore.isSuperuser (#323). Note that with PocketBase v0.23.0 superusers are converted to a system auth collection so you can always simply check the value of pb.authStore.record?.collectionName.

0.22.0

⚠️ This release introduces some breaking changes and works only with PocketBase v0.23.0+.

• Added support for sending batch/transactional create/updated/delete/upsert requests with the new batch Web APIs.

  const batch = pb.createBatch();
  batch.collection("example1").create({ ... });
  batch.collection("example2").update("RECORD_ID", { ... });
  batch.collection("example3").delete("RECORD_ID");
  batch.collection("example4").upsert({ ... });
  const result = await batch.send();

• Added support for authenticating with OTP (email code):

  const result = await pb.collection("users").requestOTP("test@example.com");
  // ... show a modal for users to check their email and to enter the received code ...
  await pb.collection("users").authWithOTP(result.otpId, "EMAIL_CODE");

  Note that PocketBase v0.23.0 comes also with Multi-factor authentication (MFA) support. When enabled from the dashboard, the first auth attempt will result in 401 response and a mfaId response, that will have to be submitted with the second auth request. For example:

... (truncated)

Commits

• 1178b3e bumped app version
• 90275cf renamed cron run argument
• 0cc8dd0 added pb.crons service
• 1137867 run prettier
• 99a5c3d added support for assigning FormData as body to individual batch requests
• 53bf1f4 added pb.realtime.onDisconnect hook
• 848b77d updated jsdoc comment
• a41d54d #324 fixed readme typos
• e802e04 fixed changelog typo
• 6ec3074 updated store test
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[janlauber]

@dependabot rebase