deepspace 0.29.1 → 0.30.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,47 @@
1
1
  # deepspace
2
2
 
3
+ ## 0.30.0
4
+
5
+ ### Minor Changes
6
+
7
+ - Remove `deepspace secrets pull`. It was a manual trigger for a mechanism that
8
+ already runs automatically at every point `.dev.vars` matters: `dev start`,
9
+ `test`, and `deploy` each refresh the cache themselves, and the hint after
10
+ `secrets set` already says to restart the dev server. Bulk export remains
11
+ `secrets download`; single values remain `secrets get --plain`.
12
+ - `deepspace rollback` now runs through the same consent gate as `undeploy`: it
13
+ prompts with the exact release about to ship (the auto-picked previous release
14
+ included), `--yes`/`-y` skips the prompt, and `--json`/non-interactive runs
15
+ without `--yes` refuse with `confirmation_required` instead of silently
16
+ rolling production back. Scripts that relied on an unconfirmed `rollback`
17
+ must add `--yes`.
18
+
19
+ ### Patch Changes
20
+
21
+ - An interrupted deploy no longer strands the next one: `deploy` reclaims a
22
+ deploy lock whose holder process is provably dead or whose lock file has
23
+ outlived the ten-minute deploy ceiling, instead of refusing with advice to
24
+ wait; and a SIGINT/SIGTERM during a locked deploy now releases the lock, says
25
+ so on stderr, and still emits the `--json` crash envelope.
26
+ - Deploy and undeploy now verify what they claim: `app undeploy` waits (bounded)
27
+ until independent fresh connections agree the host answers 404 and reports
28
+ `released` in its envelope, and `deploy` follows its edge confirmation with a
29
+ data-plane probe of the app's room namespace, reported as a separate
30
+ `dataPlane` field with a warning when Durable Object bindings are still
31
+ propagating after a redeploy.
32
+ - Secret and binding names are bounded at 256 characters at write time — a
33
+ longer name used to be accepted and then fail every later deploy at
34
+ Cloudflare's binding-name limit. When Cloudflare deterministically rejects a
35
+ worker upload, the deploy error now leads with Cloudflare's own sentence
36
+ under `worker_upload_rejected` instead of misdiagnosing it as a Cloudflare
37
+ incident and prescribing retry.
38
+ - `test run` now reports runner-level skips: a new `skippedTests` field carries
39
+ each skipped test with its authored `test.skip(cond, reason)` sentence, and a
40
+ summary line prints the distinct reasons. The `not_authenticated` refusal
41
+ ships its `auth login` action only where the bare command can succeed (an
42
+ interactive terminal, or headless with `$DEEPSPACE_EMAIL`/`$DEEPSPACE_PASSWORD`
43
+ set); otherwise the action is omitted and the message names the headless form.
44
+
3
45
  ## 0.29.1
4
46
 
5
47
  ### Patch Changes
@@ -1274,7 +1274,7 @@ function renderInlineMarkdown(value) {
1274
1274
  import { useEffect as useEffect6, useRef as useRef5, useState as useState5 } from "react";
1275
1275
 
1276
1276
  // package.json
1277
- var version = "0.29.1";
1277
+ var version = "0.30.0";
1278
1278
 
1279
1279
  // src/documentation/runtime/navigation.tsx
1280
1280
  import { Fragment as Fragment4, jsx as jsx6, jsxs as jsxs6 } from "react/jsx-runtime";
@@ -1954,4 +1954,4 @@ export {
1954
1954
  DefaultDocumentation,
1955
1955
  DocumentationContent
1956
1956
  };
1957
- //# sourceMappingURL=chunk-DWSZYN73.js.map
1957
+ //# sourceMappingURL=chunk-DIG45T65.js.map