runcloud 0.1.119 → 0.1.120

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.
Files changed (4) hide show
  1. package/dist/version.js +1 -1
  2. package/package.json +1 -1
  3. package/{runcloud-0.1.119.tgz → runcloud-0.1.120.tgz} +0 -0
  4. package/skills/run-cloud-sandboxes/SKILL.md +4 -1
package/dist/version.js CHANGED
@@ -1 +1 @@
1
- export const CLI_VERSION = '0.1.119';
1
+ export const CLI_VERSION = '0.1.120';
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "runcloud",
3
- "version": "0.1.119",
3
+ "version": "0.1.120",
4
4
  "description": "Create and control run.cloud remote mobile simulators and cloud sandboxes",
5
5
  "license": "Apache-2.0",
6
6
  "keywords": [
package/skills/run-cloud-sandboxes/SKILL.md CHANGED
@@ -286,8 +286,11 @@ printed, and lifecycle markers, interleaved in the order they happened.
286
286
  the file rather than deleting it, so a post-mortem read works on a sandbox that
287
287
  no longer exists.
288
288
 
289
- Two limits that change what you can conclude from it:
289
+ Three limits that change what you can conclude from it:
290
290
 
291
+ - A destroyed sandbox's console gets removed after 14 days (2 weeks), so a
292
+ post-mortem has a deadline. A running or paused sandbox's log is never removed,
293
+ however long it has sat quiet.
291
294
  - It is capped at 10 MiB and trimmed to the newest 5 MiB, so on a chatty workload
292
295
  early output is gone, not merely paged out. An empty-looking start is a trim,
293
296
  not proof the process printed nothing.