v0.12.2

• Update user-api-client to v0.4.0

v0.12.1

• Add and validate _userId field on all device data; update test data
• Synchronize database and collection names between localhost and deployed environments

v0.12.0

Changes:

• only time is required globally (across all device data types & upload metadata)
• in particular, timezoneOffset and conversionOffset were required and are now optional
• deviceTime is required on all device data types except cbg, where it's optional b/c of HealthKit integration
• flesh out the tests for all things globally required - for many things, there weren't any!
• timeProcessing on upload metadata now required and enforced to be one of three values: utc-bootstrapping, across-the-board-timezone, or none

Due to these changes we will be bumping _schemaVersion to 3 when deploying this.

v0.11.4

Fixes a bug in basal schema validation by adding a missing return path, without which we were trying to look up a property on a null object and crashing the service.

Surface upload errors

Updates

• return errors during the upload process in a consistent and useable form so that they can be easily surfaced in client apps

v0.11.2-prd

See jellyfish v0.11.2 release notes. This is the version for the new production env.

v0.11.2

Handles a final scheduled basal with a final-basal/fabricated-from-schedule annotation differently when retrieved as the previous to a basal (i.e., on next upload). Now will adjust the duration of the basal to match transpired reality and remove the annotation since there is no longer any uncertainty about the basal segment.

v0.11.1

v0.11.1

v0.11.0

Changes for Tandem compatibility:

• made scheduleName optional on scheduled basals
• added a minimal {target: 100} "shape" for bgTarget in wizards
• added a minimal {start: 0, target: 100} "shape" for bgTarget in pumpSettings
• removed non-existent {target: 100, low: 80, high: 120} "shape" for bgTarget in wizards and pumpSettings

The _schemaVersion will also be bumped to 2 in jellyfish's configuration during deployment. This will allow us in particular to distinguish prior required scheduleName on basals (which was not always accurately known information) from newer basals with optional scheduleName (hopefully only provided where actually known!).

v0.10.9

• AWS credentials for data bucket access are now optional if they are implicitly provided by an EC2 instance role
• Remove explicit memory constraints upon start