From f0a0114f78686f28e9535fae46d47fcd72038b1c Mon Sep 17 00:00:00 2001 From: zemion Date: Tue, 7 Jul 2026 02:54:16 +0200 Subject: [PATCH] Sync Repo-docs-RELEASE-DEPENDENCIES from project files --- Repo-docs-RELEASE-DEPENDENCIES.-.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Repo-docs-RELEASE-DEPENDENCIES.-.md b/Repo-docs-RELEASE-DEPENDENCIES.-.md index ec27904..b3ba1d8 100644 --- a/Repo-docs-RELEASE-DEPENDENCIES.-.md +++ b/Repo-docs-RELEASE-DEPENDENCIES.-.md @@ -1,4 +1,4 @@ - + > Mirrored from `/mnt/DATA/git/govoplan-core/docs/RELEASE_DEPENDENCIES.md`. > Origin: `repository`. @@ -43,6 +43,7 @@ govoplan-audit git@git.add-ideas.de:add-ideas/govoplan-audit.git v0.1.4 govoplan-files git@git.add-ideas.de:add-ideas/govoplan-files.git v0.1.4 govoplan-mail git@git.add-ideas.de:add-ideas/govoplan-mail.git v0.1.4 govoplan-campaign git@git.add-ideas.de:add-ideas/govoplan-campaign.git v0.1.4 +govoplan-calendar git@git.add-ideas.de:add-ideas/govoplan-calendar.git v0.1.4 ``` ## WebUI @@ -58,7 +59,7 @@ cd webui PATH=/home/zemion/.nvm/versions/node/v22.22.3/bin:$PATH /home/zemion/.nvm/versions/node/v22.22.3/bin/npm run build ``` -The module repositories include root-level npm package manifests so git installs can resolve `@govoplan/access-webui`, `@govoplan/admin-webui`, `@govoplan/files-webui`, `@govoplan/mail-webui`, and `@govoplan/campaign-webui` from repository roots even though their source lives below `webui/src`. +The module repositories include root-level npm package manifests so git installs can resolve `@govoplan/access-webui`, `@govoplan/admin-webui`, `@govoplan/files-webui`, `@govoplan/mail-webui`, `@govoplan/campaign-webui`, and `@govoplan/calendar-webui` from repository roots even though their source lives below `webui/src`. The normal release path is automated by `scripts/push-release-tag.sh`: it bumps or accepts the target version, updates Python/WebUI/module manifest versions, commits/tags/pushes the module repositories first, regenerates `webui/package-lock.release.json`, and then commits/tags/pushes core. If the working tree has already been bumped, pass the current version explicitly: @@ -73,7 +74,6 @@ Current tag-only module repositories: - `govoplan-addresses` - `govoplan-appointments` -- `govoplan-calendar` - `govoplan-cases` - `govoplan-connectors` - `govoplan-dms` @@ -99,14 +99,14 @@ Current tag-only module repositories: ### 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. +The supported release composition currently is the full Multi Seal Mail product: core plus access, admin, tenancy, policy, audit, files, mail, campaign, and calendar. 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. Frontend module permutations are regression-tested through `GOVOPLAN_WEBUI_MODULE_PACKAGES` and temporary build output, not through committed lockfiles for every possible combination. If a smaller composition becomes a separately shipped product, add an explicit release manifest and lockfile pair for that product, for example `package.release.files-mail.json` and `package-lock.release.files-mail.json`, generated in a clean release workspace from tagged git dependencies. ## Release Checklist - Keep Python package versions, WebUI package versions, and git tags aligned. -- Tag core, access, admin, tenancy, policy, audit, files, mail, campaign, and scaffold module repositories together. +- Tag core, access, admin, tenancy, policy, audit, files, mail, campaign, calendar, 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.