zyphr 0.1.56 → 0.1.57

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: de2fcdf8ab6779134bd46363a7c5fc6b458c05c72444a679bf6f0feba7de9bbd
-  data.tar.gz: 792f4f9353a0f31fd809afbcde76127e1a02e10f84ebc67236d33cc53e843e4d
+  metadata.gz: 5df74a41bd87130c14d2f741651f1617baade8b9ebe23f90d7edc1b112c15bc0
+  data.tar.gz: 72b9840799c7b7e72e16db2bcb96f982e5f7b9a2d4f296195d1303be7549d1fe
 SHA512:
-  metadata.gz: 700ea510741ee07471d0cc8d8128dcfed02f39b84df08eb6dd92bcaadd666d99176cd46b885e5296b751e86a96c4b8e2ec5c185ffc94e3ac55931a5934a6fc85
-  data.tar.gz: aa49c456517da6f54590d7c0fe374721b93875e4dfee83032b1b20553aa2f4260811a0484470e6e80dae518a43af092718ba5b2582d5ab3183ba0ac58d4ae896
+  metadata.gz: 7e558a85a1ffcc94bc8e692c4d7338d89632e878daf74229f7689d3b3c2236ae0500e8d375f1ee4d039836f0bd66e33ece72db481e9fb3416916d9d039eabeef
+  data.tar.gz: dc84b266eaa34edd83b5000997e8867681378d12564c1b158a492aea6c0adcabaf1d2d28e7b7c5cdc554d5d35bf4905d8f3986745613c10cc4f0030c0530dede

data/docs/DevicesApi.md

@@ -378,7 +378,7 @@ end
 
 Register a device
 
-Register a device for push notifications. If the token already exists, updates it.
+Register a device for push notifications.  Registration is an upsert keyed on (project, token), so calling it on every app launch is safe and idempotent. Re-registering an existing token under a different `user_id` **reassigns** the device to that user — the previous association does not persist, so a push addressed to the old user will not reach this device.  `user_id` is an opaque string you choose. It is stored verbatim with no foreign key, and `POST /v1/push` matches on exactly that value. No Subscriber record is created for you.  Requires a secret API key, so call it from your backend and derive `user_id` from the authenticated session rather than the request body. 
 
 ### Examples
 

data/lib/zyphr/api/devices_api.rb

@@ -339,7 +339,7 @@ module Zyphr
     end
 
     # Register a device
-    # Register a device for push notifications. If the token already exists, updates it.
+    # Register a device for push notifications.  Registration is an upsert keyed on (project, token), so calling it on every app launch is safe and idempotent. Re-registering an existing token under a different `user_id` **reassigns** the device to that user — the previous association does not persist, so a push addressed to the old user will not reach this device.  `user_id` is an opaque string you choose. It is stored verbatim with no foreign key, and `POST /v1/push` matches on exactly that value. No Subscriber record is created for you.  Requires a secret API key, so call it from your backend and derive `user_id` from the authenticated session rather than the request body. 
     # @param register_device_request [RegisterDeviceRequest] 
     # @param [Hash] opts the optional parameters
     # @return [DeviceResponse]
@@ -349,7 +349,7 @@ module Zyphr
     end
 
     # Register a device
-    # Register a device for push notifications. If the token already exists, updates it.
+    # Register a device for push notifications.  Registration is an upsert keyed on (project, token), so calling it on every app launch is safe and idempotent. Re-registering an existing token under a different `user_id` **reassigns** the device to that user — the previous association does not persist, so a push addressed to the old user will not reach this device.  `user_id` is an opaque string you choose. It is stored verbatim with no foreign key, and `POST /v1/push` matches on exactly that value. No Subscriber record is created for you.  Requires a secret API key, so call it from your backend and derive `user_id` from the authenticated session rather than the request body. 
     # @param register_device_request [RegisterDeviceRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(DeviceResponse, Integer, Hash)>] DeviceResponse data, response status code and response headers

data/spec/api/devices_api_spec.rb

@@ -96,7 +96,7 @@ describe 'DevicesApi' do
 
   # unit tests for register_device
   # Register a device
-  # Register a device for push notifications. If the token already exists, updates it.
+  # Register a device for push notifications.  Registration is an upsert keyed on (project, token), so calling it on every app launch is safe and idempotent. Re-registering an existing token under a different `user_id` **reassigns** the device to that user — the previous association does not persist, so a push addressed to the old user will not reach this device.  `user_id` is an opaque string you choose. It is stored verbatim with no foreign key, and `POST /v1/push` matches on exactly that value. No Subscriber record is created for you.  Requires a secret API key, so call it from your backend and derive `user_id` from the authenticated session rather than the request body. 
   # @param register_device_request 
   # @param [Hash] opts the optional parameters
   # @return [DeviceResponse]

data/zyphr.gemspec

@@ -17,7 +17,7 @@ require "zyphr/version"
 
 Gem::Specification.new do |s|
   s.name        = "zyphr"
-  s.version = '0.1.56'
+  s.version = '0.1.57'
   s.platform    = Gem::Platform::RUBY
   s.authors     = ["Zyphr"]
   s.email       = ["support@zyphr.dev"]

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: zyphr
 version: !ruby/object:Gem::Version
-  version: 0.1.56
+  version: 0.1.57
 platform: ruby
 authors:
 - Zyphr
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-08-16 00:00:00.000000000 Z
+date: 2026-08-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: faraday