@walkeros/cli 4.7.2-next-1791147139360 → 4.7.2-next-1791213015481
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 +24 -6
- package/dist/cli.js +1457 -1374
- package/dist/examples/flow-complete.json +52 -37
- package/dist/examples/flow-complete.md +19 -8
- package/dist/examples/index.d.ts +27 -8
- package/dist/examples/index.js +73 -47
- package/dist/examples/index.js.map +1 -1
- package/dist/index.d.ts +13 -3
- package/dist/index.js +22 -7
- package/dist/index.js.map +1 -1
- package/examples/flow-complete.json +52 -37
- package/examples/flow-complete.md +19 -8
- package/package.json +29 -29
package/CHANGELOG.md
CHANGED
|
@@ -1,9 +1,19 @@
|
|
|
1
1
|
# @walkeros/cli
|
|
2
2
|
|
|
3
|
-
## 4.7.2-next-
|
|
3
|
+
## 4.7.2-next-1791213015481
|
|
4
4
|
|
|
5
5
|
### Patch Changes
|
|
6
6
|
|
|
7
|
+
- 98398fe: `setDefaultProject` (MCP `project_manage set_default`) now needs a
|
|
8
|
+
credential instead of just a config file, works with only `WALKEROS_TOKEN`
|
|
9
|
+
set, and refuses while `WALKEROS_PROJECT_ID` names another project. The local
|
|
10
|
+
MCP server now uses `WALKEROS_PROJECT_ID` when a call names no project. New
|
|
11
|
+
export: `resolveProjectId()`.
|
|
12
|
+
- 98398fe: The `flow-complete.json` example stops an opted-out user
|
|
13
|
+
(`user.optout`) first: on the web nothing is sent, on the server the event
|
|
14
|
+
stops before dedup. Piwik PRO now gets the customer segment as custom
|
|
15
|
+
dimension 1, and the GA4 purchase rule drops its `consent`, which only
|
|
16
|
+
repeated the destination consent.
|
|
7
17
|
- ff23953: A tool refused for a missing role, scope or feature no longer
|
|
8
18
|
suggests logging in; that hint now appears only when the login is rejected or
|
|
9
19
|
missing. Project commands now report error codes such as `FORBIDDEN` in the
|
|
@@ -13,12 +23,20 @@
|
|
|
13
23
|
descriptions and the flow-complete example no longer claim that a mapping
|
|
14
24
|
rule's `consent` gates events. A rule's `consent` is not enforced yet; to
|
|
15
25
|
require consent for a destination, set `consent` in the destination's config.
|
|
26
|
+
- 98398fe: `walkeros validate` and MCP `flow_validate` now show the structural
|
|
27
|
+
warnings of a flow, such as a transformer mapping field that does nothing
|
|
28
|
+
(`TRANSFORMER_MAPPING_NO_OP`), as warnings, not errors.
|
|
29
|
+
- Updated dependencies [98398fe]
|
|
30
|
+
- Updated dependencies [98398fe]
|
|
16
31
|
- Updated dependencies [ff23953]
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
- @walkeros/
|
|
21
|
-
- @walkeros/
|
|
32
|
+
- Updated dependencies [98398fe]
|
|
33
|
+
- Updated dependencies [98398fe]
|
|
34
|
+
- Updated dependencies [98398fe]
|
|
35
|
+
- @walkeros/core@4.7.2-next-1791213015481
|
|
36
|
+
- @walkeros/collector@4.7.2-next-1791213015481
|
|
37
|
+
- @walkeros/server-core@4.7.2-next-1791213015481
|
|
38
|
+
- @walkeros/server-destination-api@4.7.2-next-1791213015481
|
|
39
|
+
- @walkeros/transformer-validate@4.7.2-next-1791213015481
|
|
22
40
|
|
|
23
41
|
## 4.7.1
|
|
24
42
|
|