GovOPlaN/govoplan
2
0
Fork 0
Code Issues 18 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Sync Repo-docs-PACKAGE-REGISTRY-RELEASES from project files

zemion
2026-08-07 02:04:51 +02:00
parent e305244825
commit 92840678d6
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Repo-docs-PACKAGE-REGISTRY-RELEASES.-.md
+6 -1
@@ -1,4 +1,4 @@
<!-- codex-wiki-sync:3689547c6bc1fb115ed86b77 --> <!-- codex-wiki-sync:d0fc47f3e46c2027eddce979 -->
> Mirrored from `/mnt/DATA/git/govoplan/docs/PACKAGE_REGISTRY_RELEASES.md`. > Mirrored from `/mnt/DATA/git/govoplan/docs/PACKAGE_REGISTRY_RELEASES.md`.
> Origin: `repository`. > Origin: `repository`.
@@ -224,6 +224,11 @@ requirements. Missing dependency/interface providers and unsupported update
windows are surfaced before an operator adds the entry to a plan; installer windows are surfaced before an operator adds the entry to a plan; installer
preflight remains authoritative. preflight remains authoritative.
Catalog entries also carry the permission definitions declared by the tagged
module manifest. Admin groups and exposes their scopes before an install or
update is planned. This is disclosure only: installing a module does not grant
its permissions to an account, role, group, tenant, or service account.
Package lifecycle and availability are intentionally separate: Package lifecycle and availability are intentionally separate:
- install, update, and uninstall change the instance-wide package composition; - install, update, and uninstall change the instance-wide package composition;