@madewithremy/admin 0.1.61 → 0.1.63
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 +19 -0
- package/dist/index.js.map +2 -2
- package/dist/ops/db.d.ts +5 -1
- package/dist/ops/usage.d.ts +24 -12
- package/dist/prod.js +30 -14
- package/dist/types/usage.d.ts +8 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,25 @@ What changed in `@madewithremy/admin`, newest first, each version under its own
|
|
|
4
4
|
|
|
5
5
|
Versions before 0.1.44 aren't recorded here.
|
|
6
6
|
|
|
7
|
+
## 0.1.63
|
|
8
|
+
|
|
9
|
+
### New
|
|
10
|
+
|
|
11
|
+
- `usage summary --scope build` (`admin.usage.summary({ scope: 'build' })`) is what Remy's work on the app cost over the window: building it, testing it in the sandbox, and its security assessments. `--scope run`, the default, is what it always was. It breaks down by model unless `--by` says otherwise, since build spend is mostly the builder's, which no method drove. `usage.view` reads both scopes.
|
|
12
|
+
- `usage summary` takes `--app <appId>`, as `issues` does: another app in the workspace with the same key, or the app to read from a laptop or CI, outside any app's workspace.
|
|
13
|
+
- The summary's result carries `scope`.
|
|
14
|
+
|
|
15
|
+
### Changed behavior
|
|
16
|
+
|
|
17
|
+
- A branch preview now runs on a copy of the pusher's dev database, taken by its build at the push, never on a copy of live: `previews` help says so. A push with no dev database behind it (an API key's, a clone outside the editor) gets the branch's tables, empty, and a preview whose branch has had no push for 30 days is retired until the next push. Check for: a test that reads production rows through a preview.
|
|
18
|
+
|
|
19
|
+
## 0.1.62
|
|
20
|
+
|
|
21
|
+
### Changed behavior
|
|
22
|
+
|
|
23
|
+
- `db history attach` (`admin.db.historyAttach()`) is refused for a past database larger than 1 GB, as a `sql_error` that says so, since the attach copies it for every call. Read what you need with `db history query` and write it to live with `db query` instead. Check for: a repair script that attaches a large past database.
|
|
24
|
+
- `db history query` and `db history attach` can answer a `sql_error` saying the server has no room to copy the past database right now. Nothing was applied; try again shortly.
|
|
25
|
+
|
|
7
26
|
## 0.1.61
|
|
8
27
|
|
|
9
28
|
### New
|