@pikku/deploy 0.12.12 → 0.12.14
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 +14 -0
- package/dist/manifest.d.ts +9 -0
- package/dist/provider-adapter.d.ts +5 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,19 @@
|
|
|
1
1
|
# @pikku/deploy
|
|
2
2
|
|
|
3
|
+
## 0.12.14
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 5a50446: deploy.embed puts files into a standalone binary, so a project ships with the assets it reads at runtime.
|
|
8
|
+
|
|
9
|
+
## 0.12.13
|
|
10
|
+
|
|
11
|
+
### Patch Changes
|
|
12
|
+
|
|
13
|
+
- cf40182: Deployed units that call `rpc.startWorkflow('x')` now get x's meta, so the call no longer fails with `WorkflowNotFoundError`. The inspector records `startsWorkflows` for literal `rpc.startWorkflow(...)` calls. It warns when a handler computes the workflow name or passes `rpc` to a helper, because the planner cannot see those calls.
|
|
14
|
+
|
|
15
|
+
With workflow queues, the deploy planner gives a starter unit the workflow meta and orchestrator queue meta only (new `--workflowMeta` filter), plus `workflow-state` and `queue` services. Without queues the start runs inline, so the whole workflow is bundled. Core's `startWorkflow` now requires the workflow registration only for inline runs; queued runs need only the meta.
|
|
16
|
+
|
|
3
17
|
## 0.12.12
|
|
4
18
|
|
|
5
19
|
### Patch Changes
|
package/dist/manifest.d.ts
CHANGED
|
@@ -86,6 +86,15 @@ export interface DeploymentUnit {
|
|
|
86
86
|
* registered here as well as in its own gateway unit.
|
|
87
87
|
*/
|
|
88
88
|
invokedAgents?: string[];
|
|
89
|
+
/**
|
|
90
|
+
* Workflows a function in this unit starts by literal name with
|
|
91
|
+
* `rpc.startWorkflow(...)`, when the unit is not already a full
|
|
92
|
+
* workflow-state unit. With workflow queues, per-unit codegen bundles only
|
|
93
|
+
* their meta: a queued start creates the run from it and hands the run to
|
|
94
|
+
* the workflow's orchestrator unit, which holds the registration. Without
|
|
95
|
+
* them the start runs inline, so the whole workflow is bundled.
|
|
96
|
+
*/
|
|
97
|
+
startedWorkflows?: string[];
|
|
89
98
|
/** SHA-256 of final bundled artifact (set by build pipeline) */
|
|
90
99
|
bundleHash?: string;
|
|
91
100
|
/** Final bundle size in bytes (set by build pipeline) */
|
|
@@ -60,6 +60,11 @@ export interface EntryGenerationContext {
|
|
|
60
60
|
* incident.
|
|
61
61
|
*/
|
|
62
62
|
version?: string;
|
|
63
|
+
/**
|
|
64
|
+
* Whether the build staged `deploy.embed` files, which the entry exports to
|
|
65
|
+
* the app as `PIKKU_EMBEDDED_<NAME>` paths.
|
|
66
|
+
*/
|
|
67
|
+
embedded?: boolean;
|
|
63
68
|
/**
|
|
64
69
|
* The database the generated entry has to open for itself, or undefined when
|
|
65
70
|
* the project has none.
|