@pikku/skills 0.12.17 → 0.12.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/CHANGELOG.md +22 -0
- package/dist/skills.gen.js +1 -1
- package/package.json +1 -1
- package/skills/pikku-fabric/SKILL.md +6 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,27 @@
|
|
|
1
1
|
# @pikku/skills
|
|
2
2
|
|
|
3
|
+
## 0.12.18
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 7d8082a: Add `pikku fabric variables set` and `pikku fabric variables get`
|
|
8
|
+
|
|
9
|
+
`secrets` was the only stage-scoped store the CLI exposed, so a value declared
|
|
10
|
+
with `defineVariable` could be set locally through `.env` and not at all on a
|
|
11
|
+
deployed stage — `variables.get('NAME')` compiled, ran, and answered `undefined`
|
|
12
|
+
forever, with nothing saying why. The fabric API already had
|
|
13
|
+
`setStageConsoleVariable` and `getStageConsoleVariable`; only the CLI surface was
|
|
14
|
+
missing.
|
|
15
|
+
|
|
16
|
+
`set` stores the value the way `LocalVariablesService` reads one: `JSON.parse`,
|
|
17
|
+
falling back to the raw string. `--value true` is therefore the boolean on a
|
|
18
|
+
stage exactly as it is from `.env`, and `--value '"true"'` is the string. `get`
|
|
19
|
+
prints the stored value as JSON so the two are distinguishable, which is usually
|
|
20
|
+
why you are looking.
|
|
21
|
+
|
|
22
|
+
Variables are not sealed and are readable back — that is the difference from
|
|
23
|
+
`secrets`, and anything that would hurt to print belongs in `secrets set`.
|
|
24
|
+
|
|
3
25
|
## 0.12.17
|
|
4
26
|
|
|
5
27
|
### Patch Changes
|