add-ideas/govoplan-core
1
0
Fork 0
Code Issues 45 Pull Requests Actions Packages Projects Releases Wiki Activity

Sync Repo-docs-RELEASE-DEPENDENCIES from project files

zemion
2026-07-07 09:12:50 +02:00
parent 6d12c74f5c
commit 3147c7deb7
1 changed files with 28 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
Repo-docs-RELEASE-DEPENDENCIES.-.md

@@ -1,4 +1,4 @@
<!-- codex-wiki-sync:139ec2a4b3b9d5c798d4508c -->
<!-- codex-wiki-sync:4ac4cee4a2b691e1751522a9 -->
> Mirrored from `/mnt/DATA/git/govoplan-core/docs/RELEASE_DEPENDENCIES.md`.
> Origin: `repository`.
@@ -53,18 +53,37 @@ already installed. It does not install or uninstall Python/npm packages from
inside the running server.
For runtime package changes, create an operator install plan in Admin > System >
Modules. The plan can also be rendered from the server shell:
Modules. The module manager shows the trusted installer preflight status and
blocks unsafe uninstalls before the operator touches packages.
Preflight from the server shell:
```bash
govoplan-module-install-plan --format shell
# or
python -m govoplan_core.commands.module_install_plan --format shell
govoplan-module-installer --format shell
```
Apply those commands from a controlled operator shell while maintenance mode is
active. Install rows must use tagged package/git refs or registry packages, not
local `file:` or workspace links. After package changes, run migrations and
restart or reload the affected server/WebUI processes according to the
Apply from a controlled operator shell while maintenance mode is active:
```bash
govoplan-module-installer --apply --build-webui
```
The installer uses a runtime lock, snapshots `pip freeze` plus WebUI
`package.json`/`package-lock.json`, writes a run record below
`runtime/module-installer/runs`, and marks planned rows as applied only after
all commands succeed.
Rollback uses the saved run snapshot:
```bash
govoplan-module-installer --rollback <run-id>
```
Install rows must use tagged package/git refs or registry packages, not local
`file:` or workspace links. WebUI package changes still require `npm install`
and a WebUI rebuild/reload because the current shell resolves WebUI modules from
the build-time package graph. After backend package changes, run migrations and
restart or reload the affected server/worker processes according to the
deployment model.
## WebUI