@protobase/cli 0.73.3 → 0.73.4

package/dist/cli/package.js

@@ -1,4 +1,4 @@
 //#region package.json
-var version = "0.73.3";
+var version = "0.73.4";
 //#endregion
 export { version };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@protobase/cli",
-  "version": "0.73.3",
+  "version": "0.73.4",
   "description": "The protobase command: scaffold, doctor, dev, build and serve a Protobase project.",
   "license": "Apache-2.0",
   "repository": {
@@ -43,13 +43,13 @@
   "dependencies": {
     "@better-auth/core": "^1.7.12",
     "@hono/node-server": "^2.1.3",
-    "@protobase/config": "0.73.3",
-    "@protobase/layout": "0.73.3",
-    "@protobase/query": "0.73.3",
-    "@protobase/schema": "0.73.3",
-    "@protobase/server": "0.73.3",
-    "@protobase/ui": "0.73.3",
-    "@protobase/workflows": "0.73.3",
+    "@protobase/config": "0.73.4",
+    "@protobase/layout": "0.73.4",
+    "@protobase/query": "0.73.4",
+    "@protobase/schema": "0.73.4",
+    "@protobase/server": "0.73.4",
+    "@protobase/ui": "0.73.4",
+    "@protobase/workflows": "0.73.4",
     "@react-email/render": "^2.1.0",
     "@scalar/hono-api-reference": "^0.12.10",
     "@sentry/vite-plugin": "^11.10.0",

package/skills/protobase/references/features/notifications.md

@@ -11,7 +11,7 @@ A bell in the top bar and push to browsers and phones, for what your app tells i
 - [Sending notifications](../reference/notifications.md#sending) (beta): Your code sends a notification to users or to devices as a background job, queued in the same transaction as a write, and says on each one whether it shows in the inbox.
 - [Notification history](../reference/notifications.md#history) (beta): Each user's inbox notifications are kept with when they were read, and the API lists them, counts the unread ones and marks them read.
 - [Web Push](../reference/notifications.md#web-push) (beta): Notifications reach desktop and Android browsers and home-screen web apps on iPhone through Web Push, with keys you generate.
-- [Push on Android](../reference/notifications.md#android) (in development): The mobile app receives notifications on Android through Firebase Cloud Messaging, set up by `protobase mobile` from a `google-services.json` in the project.
+- [Push on Android](../reference/notifications.md#android) (in development): The server sends notifications to Android devices through Firebase Cloud Messaging with the service account key in `PROTOBASE_FCM_SERVICE_ACCOUNT`; the mobile app registering for them is coming soon.
 - Push on iOS (coming soon): Notifications reach the iOS build of the app on a user's iPhones and iPads.
 - [Do not disturb](../reference/status.md#do-not-disturb) (beta): While someone is on do not disturb, sends push nothing to their devices and keep inbox notifications in the bell for later.
 - [Notification bell](../reference/notifications.md#the-bell) (beta): The top bar shows how many inbox notifications are unread; its panel opens each one, marks them read and turns push on or off for this device.

package/skills/protobase/references/reference/notifications.md

@@ -221,7 +221,7 @@ Android devices receive push through Firebase Cloud Messaging's HTTP v1 API. You
 
 JSON that is not a service account key, a `project_id` that is not a Google project id, or a `private_key` that is not an RSA key of at least 2048 bits stops startup, naming the variable without its value. The key is a secret: keep it out of client code, `VITE_` variables and the repository. Anyone holding it can push to every Android device of the project.
 
-The server signs in as the service account with a token scoped to sending through FCM only, and keeps one token until five minutes before it expires. Requests go only to Google's token endpoint and to FCM, for the key's own project, never through a redirect; the URLs in the key's JSON are not read. A device is removed only when FCM reports its token unregistered. Any other refusal, such as a key without access to the project, keeps the device and retries it. A device stored with a token that is not an FCM token is `refused`.
+The server signs in as the service account with a token scoped to sending through FCM only, and keeps one token until five minutes before it expires. When no token can be had before the first request, the send fails with nothing pushed and is retried; a token that fails later retries only the devices still waiting for one. Requests go only to Google's token endpoint and to FCM, for the key's own project, never through a redirect; the URLs in the key's JSON are not read. A device is removed only when FCM reports its token unregistered. Any other refusal, such as a key without access to the project, keeps the device and retries it. A device stored with a token that is not an FCM token is `refused`.
 
 A message's title and body are the notification. Its `data` and `url` reach the app as FCM's data, each value a string (other JSON as its text), with `user`, the id of the user the device is registered for, over any `user` given. Its `ttl`, `urgency`, `tag`, `sound` and `badge` set the Android delivery and notification. A message's `platform.fcm` is merged over these, and may set only: