Skip to content

docs(build): say the CI publish-and-install step is all-or-nothing #382

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zhuangjianguo merged 1 commit into from
Oct 29, 2026
Merged

docs(build): say the CI publish-and-install step is all-or-nothing #382

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions content/docs/build/packages.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -154,6 +154,9 @@ Package ids in install commands are the stable manifest id
> and install in one step: `os package publish --env <id> --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 —
Expand Down
Loading