@lunora/queue 1.0.0-alpha.66 → 1.0.0-alpha.68

package/dist/index.d.mts

@@ -220,12 +220,15 @@ interface CapturedQueueMessage {
    * true of the deployed broker only as far as Lunora's binding reconcile (run
    * by `lunora dev`, `deploy` and `prepare`) keeps the two in step: it writes
    * every declared tuning field onto the consumer, including onto one that
-   * already exists. It does NOT remove a field taken out of `defineQueue` —
-   * dropping `deadLetterQueue` leaves the deployed DLQ in place, so this then
-   * reads `false` for messages that were in fact dead-lettered — and it never
-   * writes wrangler's `env.<name>` blocks, so a `--env` deploy uses whatever
-   * that block says. A bare `wrangler deploy` over a hand-edited consumer can
-   * disagree too, and nothing on this side can see any of it.
+   * already exists, and takes a field back out once `defineQueue` drops it
+   * (it records what `defineQueue` declared in `package.json`
+   * `lunora.queueTuning`). The gaps that remain: a field changed by hand to
+   * another value than the declared one is
+   * kept when the declaration drops it, so a hand-set DLQ still reads
+   * `false` here; a `--env` deploy retunes the `env.<name>` consumers but
+   * never writes their `dead_letter_queue`, which that block names itself;
+   * and a bare `wrangler deploy` over a hand-edited consumer can disagree
+   * too. Nothing on this side can see any of it.
    */
   deadLettered: boolean;
   /** Handler error message when `outcome` is `error`; absent otherwise. */

package/dist/index.d.ts

@@ -220,12 +220,15 @@ interface CapturedQueueMessage {
    * true of the deployed broker only as far as Lunora's binding reconcile (run
    * by `lunora dev`, `deploy` and `prepare`) keeps the two in step: it writes
    * every declared tuning field onto the consumer, including onto one that
-   * already exists. It does NOT remove a field taken out of `defineQueue` —
-   * dropping `deadLetterQueue` leaves the deployed DLQ in place, so this then
-   * reads `false` for messages that were in fact dead-lettered — and it never
-   * writes wrangler's `env.<name>` blocks, so a `--env` deploy uses whatever
-   * that block says. A bare `wrangler deploy` over a hand-edited consumer can
-   * disagree too, and nothing on this side can see any of it.
+   * already exists, and takes a field back out once `defineQueue` drops it
+   * (it records what `defineQueue` declared in `package.json`
+   * `lunora.queueTuning`). The gaps that remain: a field changed by hand to
+   * another value than the declared one is
+   * kept when the declaration drops it, so a hand-set DLQ still reads
+   * `false` here; a `--env` deploy retunes the `env.<name>` consumers but
+   * never writes their `dead_letter_queue`, which that block names itself;
+   * and a bare `wrangler deploy` over a hand-edited consumer can disagree
+   * too. Nothing on this side can see any of it.
    */
   deadLettered: boolean;
   /** Handler error message when `outcome` is `error`; absent otherwise. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lunora/queue",
-  "version": "1.0.0-alpha.66",
+  "version": "1.0.0-alpha.68",
   "description": "Cloudflare Queues for Lunora: defineQueue producers + consumers, the ctx.queues surface, and the generated queue() worker handler",
   "keywords": [
     "background-jobs",
@@ -45,7 +45,7 @@
   },
   "dependencies": {
     "@lunora/errors": "1.0.0-alpha.41",
-    "@lunora/platform": "1.0.0-alpha.37"
+    "@lunora/platform": "1.0.0-alpha.38"
   },
   "engines": {
     "node": "^22.15.0 || >=24.11.0"