@amaster.ai/employee-runtime-connector 0.1.0-beta.11 → 0.1.0-beta.2
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/README.md +0 -2
- package/dist/amaster-runtime-daemon.mjs +91 -1177
- package/dist/amaster-runtime.mjs +1 -23
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -21,8 +21,6 @@ Do not use `latest`, `^`, or `~` in a runtime image. The image tag and connector
|
|
|
21
21
|
|
|
22
22
|
Immutable images should pin an exact package version as their baseline. The current connector does not download or replace runtime code while running; package upgrades and rollbacks belong to the image build and rollout.
|
|
23
23
|
|
|
24
|
-
The publish workflow verifies that npm records the publishing commit as the package `gitHead`, then updates the repository deployment pin. Remote deployment accepts that package only when its `gitHead` is an ancestor of the target source commit and the connector package path is unchanged between them. This path-only comparison is valid because the published connector is self-contained; if runtime code starts importing workspace source outside this package, expand the provenance scope and tests before release. After restart, deployment also verifies the package CLI version inside the container. Do not update the deployment pin manually to bypass either provenance check.
|
|
25
|
-
|
|
26
24
|
## Package Contents
|
|
27
25
|
|
|
28
26
|
- `dist/amaster-runtime.mjs`: configuration, pairing, workspace, diagnostics, and daemon lifecycle CLI.
|