From f77bf665347a49753fbe51103ec1c949873f2a27 Mon Sep 17 00:00:00 2001
From: zemion <albrecht@degering.name>
Date: Mon, 6 Jul 2026 23:18:38 +0200
Subject: [PATCH] Sync Repo-docs-RELEASE-DEPENDENCIES from project files

---
 Repo-docs-RELEASE-DEPENDENCIES.-.md | 33 +++++++++++++++++++++++++++--
 1 file changed, 31 insertions(+), 2 deletions(-)

diff --git a/Repo-docs-RELEASE-DEPENDENCIES.-.md b/Repo-docs-RELEASE-DEPENDENCIES.-.md
index 94ec0db..58e172c 100644
--- a/Repo-docs-RELEASE-DEPENDENCIES.-.md
+++ b/Repo-docs-RELEASE-DEPENDENCIES.-.md
@@ -1,4 +1,4 @@
-<!-- codex-wiki-sync:889d7405d19b25f4db62adf8 -->
+<!-- codex-wiki-sync:fb4ad06a7a8d8929326faaef -->
 
 > Mirrored from `/mnt/DATA/git/govoplan-core/docs/RELEASE_DEPENDENCIES.md`.
 > Origin: `repository`.
@@ -67,6 +67,35 @@ cd /mnt/DATA/git/govoplan-core
 scripts/push-release-tag.sh --version 0.1.2
 ```
 
+The script also includes GovOPlaN roadmap/scaffold module repositories that do not yet have package metadata. Those repositories are committed, tagged, and pushed with the same release tag, but they are tag-only until they contain `pyproject.toml`, module manifests, or WebUI packages. Tag-only repositories are not listed in `requirements-release.txt` or `webui/package.release.json`.
+
+Current tag-only module repositories:
+
+- `govoplan-addresses`
+- `govoplan-appointments`
+- `govoplan-calendar`
+- `govoplan-cases`
+- `govoplan-connectors`
+- `govoplan-dms`
+- `govoplan-erp`
+- `govoplan-fit-connect`
+- `govoplan-forms`
+- `govoplan-identity-trust`
+- `govoplan-idm`
+- `govoplan-ledger`
+- `govoplan-notifications`
+- `govoplan-ops`
+- `govoplan-payments`
+- `govoplan-portal`
+- `govoplan-reporting`
+- `govoplan-search`
+- `govoplan-tasks`
+- `govoplan-templates`
+- `govoplan-workflow`
+- `govoplan-xoev`
+- `govoplan-xrechnung`
+- `govoplan-xta-osci`
+
 ### Release lockfile strategy
 
 The supported release composition currently is the full Multi Seal Mail product: core plus access, admin, tenancy, policy, audit, files, mail, and campaign. Keep one committed full-product release lockfile at `webui/package-lock.release.json`, generated from `webui/package.release.json` in a clean release workspace. Development `package-lock.json` may continue to point at local `file:` dependencies.
@@ -76,7 +105,7 @@ Frontend module permutations are regression-tested through `GOVOPLAN_WEBUI_MODUL
 ## Release Checklist
 
 - Keep Python package versions, WebUI package versions, and git tags aligned.
-- Tag core, access, admin, tenancy, policy, audit, files, mail, and campaign repositories together.
+- Tag core, access, admin, tenancy, policy, audit, files, mail, campaign, and scaffold module repositories together.
 - Update `requirements-release.txt` and `webui/package.release.json` when the release tag changes.
 - Generate the committed full-product release lockfile from `package.release.json` with `scripts/generate-release-lock.sh`.
 - Add separate release manifest/lockfile pairs only for module compositions that are shipped as their own products.