From 8c101ed6612747f3d65e18e2d29682b82d07acfa Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 29 Oct 2026 04:23:34 +0000 Subject: [PATCH] docs(build): say the CI publish-and-install step is all-or-nothing A refused install publishes nothing: no version is stored and the command exits non-zero, so a pipeline sees the failure. Co-Authored-By: Claude Claude-Session: https://claude.ai/code/session_01QsR2jQwak4m4H1Ta2cvPgZ --- content/docs/build/packages.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/docs/build/packages.mdx b/content/docs/build/packages.mdx index c01cef9..ec2fca2 100644 --- a/content/docs/build/packages.mdx +++ b/content/docs/build/packages.mdx @@ -154,6 +154,9 @@ Package ids in install commands are the stable manifest id > and install in one step: `os package publish --env --install > [--seed-sample-data]`. This is a convenience for automation, not the path a > person uses — interactive installs happen in the environment's Marketplace. +> The step is all-or-nothing: if the install is refused, nothing is published — +> no version is stored and the command exits non-zero, so the pipeline sees the +> failure. Install merges the package's metadata into the live kernel, registers its objects with ObjectQL, and seeds initial data on first install —