92 lines
4.6 KiB
Markdown
92 lines
4.6 KiB
Markdown
# Integrity and performance source release — September 2026
|
|
|
|
Coordinated tracking: [Core #298](https://git.add-ideas.de/GovOPlaN/govoplan-core/issues/298).
|
|
This source publication advances only the affected packages; it is not a signed
|
|
catalog publication, runtime-image release, or remote production rollout.
|
|
|
|
## Package set
|
|
|
|
| Package | Version |
|
|
| --- | --- |
|
|
| Core / developer meta-package | 0.1.46 |
|
|
| Addresses | 0.1.23 |
|
|
| Calendar | 0.1.24 |
|
|
| Campaign | 0.1.29 |
|
|
| Cases | 0.1.25 |
|
|
| Committee | 0.1.22 |
|
|
| Connectors | 0.1.27 |
|
|
| Dataflow | 0.1.25 |
|
|
| Datasources | 0.1.26 |
|
|
| Files | 0.1.27 |
|
|
| Forms Runtime | 0.1.22 |
|
|
| IDM | 0.1.26 |
|
|
| Mail | 0.1.28 |
|
|
| Reporting | 0.1.22 |
|
|
| Tickets | 0.1.23 |
|
|
|
|
Consumers of new Core helpers require Core 0.1.46 or later. Dataflow and
|
|
Datasources also require the matching Core WebUI contract. The release manifests,
|
|
immutable Git lock, and developer package describe this coordinated composition.
|
|
Unchanged packages retain their independent versions.
|
|
|
|
## Database and data integrity
|
|
|
|
The reviewed additive heads are Connectors `d2a4c6e8f0b1`, Datasources
|
|
`e2b8d4a0f6c3`, Files `a2b3c4d5e701`, and Mail `b5d6e7f8091a`.
|
|
Back up the target deployment and rehearse its normal upgrade before rollout.
|
|
Never downgrade away retained CSV originals without a separate recovery plan.
|
|
Files preserves historical duplicate copies; Mail leaves legacy maildrop identity
|
|
unset rather than guessing an account. A schema upgrade does not authorize POP3
|
|
retrieval/reconciliation, provider deletion, or message resending.
|
|
|
|
Development startup may automatically apply pending migrations after a watched
|
|
source change. Therefore, inspect actual Alembic heads and schema before assuming
|
|
a live development database is still at its pre-change state. A backup taken
|
|
after such an upgrade is a current-state recovery copy, not a pre-upgrade backup.
|
|
|
|
On 8 September, the local PostgreSQL development database already contained all
|
|
four heads. Schema and constraint inspection passed; recomputing the Files
|
|
identity backfill checked 7,385 rows with zero mismatches. A private current-state
|
|
database backup was created. Per-instance backup paths and row contents are not
|
|
published in this repository. The implementation's initial receipt claiming no
|
|
live migration occurred was incorrect: watched development-server restarts had
|
|
applied the migration files automatically. Restoring the backup into an isolated
|
|
PostgreSQL 16 cluster and running the normal upgrade preserved all 281 public
|
|
tables, 142,287 rows, and migration heads exactly. Both Datasources PostgreSQL
|
|
concurrency regressions passed. The test-only cluster was then stopped.
|
|
|
|
Release preparation additionally corrected Alembic's ConfigParser handling of
|
|
percent-escaped connection URLs, preserving the exact database URL. The static
|
|
migration auditor now recognizes the existing reviewed development-wrapper
|
|
aliases and peer filenames without executing migration code; historical
|
|
migrations are unchanged.
|
|
|
|
## Verification and boundaries
|
|
|
|
The implementation passed the required focused workspace gate, including 63
|
|
frontend build configurations and 230 browser conformance tests. Owning-module
|
|
regressions cover exact import/rollback evidence, authorization-before-pagination,
|
|
bounded recurrence and response processing, collision-safe attachment naming,
|
|
and stale asynchronous UI completion. English/German feature documentation stays
|
|
in each owning module; Core documents shared integrity contracts.
|
|
|
|
Mock-provider tests and local work-count measurements do not establish production
|
|
throughput or provider race behavior. Real S3/SMB/Seafile and POP3 acceptance,
|
|
representative load testing, and deployment authentication checks remain separate
|
|
operational validation. Source tags trigger package workflows; a pushed source
|
|
tag alone does not prove a registry artifact or signed catalog is published.
|
|
|
|
## Deutsch
|
|
|
|
Dieses koordinierte Quellrelease veröffentlicht nur die betroffenen Pakete.
|
|
Produktions-Images, signierter Modulkatalog und entfernte Produktivinstanzen
|
|
werden dadurch nicht ausgerollt. Die vier Migrationen bewahren bestehende Daten;
|
|
historische POP3-Zuordnungen werden nicht geraten. POP3 ist ein eigener
|
|
Import-Arbeitsablauf innerhalb von **Mail**, kein separat installierbares Modul.
|
|
|
|
Der Entwicklungsserver kann Migrationen beim automatischen Neustart nach einer
|
|
Quelländerung bereits anwenden. Tatsächliche Schema-Stände prüfen; eine danach
|
|
erstellte Sicherung enthält den aktuellen Stand und ist keine Sicherung vor dem
|
|
Upgrade. Externe Transportaktionen, erneutes Versenden und Löschungen werden
|
|
durch die Migration oder Quellveröffentlichung nicht ausgelöst.
|