anchordb 1.3.0 → 1.3.2

package/CHANGELOG.md

@@ -5,6 +5,35 @@ All notable changes to the `anchordb` packages.
 This project follows [semantic versioning](https://semver.org/). While the version is `0.x`, minor
 releases may contain breaking changes.
 
+## 1.3.2
+
+Documentation only — no code changes.
+
+- **Bugs, support and feedback go to the AnchorDB project page**, at
+  [nisalanadeera.com/projects/anchordb](https://www.nisalanadeera.com/projects/anchordb#feedback): a form
+  that asks for the package, version and platform, and a reply by email.
+- Every package's npm **Homepage** is that page, and **Report a bug** (`npm bugs`) opens the form.
+- Every README links the overview and the form, and says what a bug report that can be acted on
+  includes.
+- The package READMEs' family tables list all six packages, with `anchordb-lens-link`.
+- All six packages move to 1.3.2 together.
+
+## 1.3.1
+
+**Lens Link keeps both apps running in the background.** Found on a phone: switching from the app to
+Anchor Lens let the phone stop the app within seconds, and the link went with it.
+
+- `anchordb-lens-link`: while the link is on, the app runs an Android foreground service with an
+  ongoing notification — *Anchor Lens Link on*, then *Anchor Lens connected* — which is what Android
+  lets an app use to keep running. `keepAlive: false` turns it off; `link.keepAliveError` says why it
+  could not start.
+- `startKeepAlive`, `updateKeepAlive` and `stopKeepAlive` keep a client running the same way. Anchor
+  Lens uses them while it is connected to an app, so you can switch between the two.
+- `backgroundStatus()`, `askNotificationPermission()`, `askBatteryUnrestricted()`,
+  `openNotificationSettings()` and `openBackgroundSettings()`: the permissions and settings that stop a
+  phone overruling it, including Xiaomi's Autostart screen.
+- Only `anchordb-lens-link` changes. The other packages stay at 1.3.0.
+
 ## 1.3.0
 
 **Anchor Lens Link: open a QA build's database in Anchor Lens on the same phone, from a file.** Asked

package/README.md

@@ -3,6 +3,8 @@
 **MongoDB + Mongoose, for mobile apps.** A local, persistent document database with a
 Mongoose-shaped API that works completely offline — and *optionally* synchronises with a backend.
 
+**[Overview](https://www.nisalanadeera.com/projects/anchordb)** · **[Report a bug or get support](https://www.nisalanadeera.com/projects/anchordb#feedback)**
+
 ```bash
 npm install anchordb
 ```
@@ -157,7 +159,7 @@ server-side change streams, text/`2dsphere`/hashed indexes, collation, and the
 
 ## The AnchorDB family
 
-Five packages. **Only `anchordb` is required** — the rest exist so that an offline-only app never
+Six packages. **Only `anchordb` is required** — the rest exist so that an offline-only app never
 has to download Express, and an Express server never has to download React.
 
 | Package | What it is | Runs where |
@@ -167,11 +169,28 @@ has to download Express, and an Express server never has to download React.
 | [`anchordb-angular`](https://www.npmjs.com/package/anchordb-angular) | Angular / Ionic module, DI and RxJS observables | the device |
 | [`anchordb-sync-server`](https://www.npmjs.com/package/anchordb-sync-server) | Server half of sync — Express, NestJS, Next.js | your backend |
 | [`anchordb-relay`](https://www.npmjs.com/package/anchordb-relay) | Dev relay for the Anchor Lens inspector | your laptop |
+| [`anchordb-lens-link`](https://www.npmjs.com/package/anchordb-lens-link) | Open a QA build's database in Anchor Lens on the same phone, from a file | the device, in QA builds |
 
 Each one needs a different third-party framework as a peer dependency, and npm resolves those per
 package rather than per import — which is why they are not one package. Full reasoning and API
 reference: [github.com/knnadeera/anchordb](https://github.com/knnadeera/anchordb).
 
+## Bugs, support and feedback
+
+Report a bug, ask for help or suggest a feature on the [AnchorDB project page](https://www.nisalanadeera.com/projects/anchordb#feedback) —
+choose `anchordb` as the package, and the reply comes by email.
+
+A report that can be acted on straight away has:
+
+- the package and exact version — what `npm ls anchordb` prints
+- where it runs — Expo, Ionic, a browser or Node — and which storage adapter
+- the smallest snippet that reproduces it
+- the full error, including `code`, `keyPattern` and `keyValue` for an E11000
+- what you expected to happen instead
+
+**Sync problems:** say which conflict strategy you use, and whether the mutation shows as parked in
+Anchor Lens — a push rejected by a unique index is parked rather than retried forever.
+
 ## License
 
 MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "anchordb",
-  "version": "1.3.0",
+  "version": "1.3.2",
   "description": "MongoDB + Mongoose for mobile apps. Offline-first local database with optional sync.",
   "keywords": [
     "mongodb",
@@ -156,9 +156,9 @@
     "url": "git+https://github.com/knnadeera/anchordb.git",
     "directory": "packages/core"
   },
-  "homepage": "https://github.com/knnadeera/anchordb#readme",
+  "homepage": "https://www.nisalanadeera.com/projects/anchordb",
   "bugs": {
-    "url": "https://github.com/knnadeera/anchordb/issues"
+    "url": "https://www.nisalanadeera.com/projects/anchordb#feedback"
   },
   "attw": {
     "ignoreRules": [