@camstack/develop 0.1.17 → 0.1.18
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/package.json
CHANGED
|
@@ -86,7 +86,7 @@ own secrets), D798 (an addon reads its own settings resolved).
|
|
|
86
86
|
child from a file or a pipe the child reads, never from a string you log.
|
|
87
87
|
- Client-side developer tooling is different: the `camstack` CLI's
|
|
88
88
|
`$CAMSTACK_TOKEN` / `--token-file` and `scripts/hub/hub.mjs`'s credential chain
|
|
89
|
-
(`--token-file`,
|
|
89
|
+
(`--token-file`, then the `camstack login` session) are a developer's own credentials on their own machine,
|
|
90
90
|
not server-side secrets.
|
|
91
91
|
|
|
92
92
|
## 5. Logs, fixtures, the repository
|
package/skills/track-review.md
CHANGED
|
@@ -26,7 +26,7 @@ The server reads three environment variables. Nothing else, no flags.
|
|
|
26
26
|
|
|
27
27
|
TLS verification is never turned off: a certificate error is fixed by naming the
|
|
28
28
|
CA, not by disabling the check. Triage and frame need a normal token;
|
|
29
|
-
**apply needs
|
|
29
|
+
**apply needs admin permissions** and shows the hub's own refusal if the token
|
|
30
30
|
lacks it. Tokens are never printed.
|
|
31
31
|
|
|
32
32
|
```json
|