ek9_deploy_package

Answers with status and bundlePath after publishing one package's SOURCE bundle to the configured remote registry; packages and generates missing signing keys first.

Category: Execution · Compare: mvn deploy / cargo publish / npm publish

When to use it

'Publish this package to the registry' is one call with file:'package.ek9' and confirm:true. The last release step after tests pass and the version is bumped; it packages and generates missing signing keys itself.

When not to use it

Building the bundle locally with no remote push - use ek9_package.
Installing into the LOCAL library rather than publishing - use ek9_install_package.
Bumping the version first - ek9_increment_version, then deploy.

Details

IRREVERSIBLE: the bundle becomes visible to every consumer of the shared registry, hence the confirm:true guard, checked before any fork. Pushes the SOURCE bundle (.ek9 files + manifest + capabilities), not bytecode; the registry is workspace-configured (no registry parameter). Failures are named by stage - compile-failed (exit 8), tests-failed, coverage-low, timed-out after 120s, failed for a registry error such as an unreachable host or a version already deployed (bump with ek9_increment_version and retry).

Arguments

Argument	Type	Required	What it is
`confirm`	boolean	yes	Must be true: acknowledges that the package becomes visible to other consumers of the registry and cannot be retracted.
`file`	string	yes	The .ek9 file holding the 'defines package' block, workspace-relative (typically 'package.ek9'); an absolute path inside the workspace is accepted.
`verbosity`	string: full \| summary \| none		Response size. The default answers with status, summary and bundlePath; 'full' adds the CLI's stdout, argv, exitCode, elapsedMs and timedOut.

Recorded calls

Real calls, recorded against small projects and checked on every build - a changed answer fails it.

Missing confirm guard

Request

{
  "file" : "<workspace-root>/package.ek9"
}

Response

{
  "error" : {
    "kind" : "missing-confirmation",
    "message" : "Deployment publishes to a shared registry and cannot be retracted; confirm must be true"
  },
  "meta" : {
    "serverMs" : "<timing>"
  },
  "nextStep" : "re-call with confirm:true",
  "status" : "refused",
  "summary" : "refused: Deployment publishes to a shared registry and cannot be retracted; confirm must be true"
}