Skip to content

Update Architecture Decision Records #2475

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −5
Open

Update Architecture Decision Records #2475

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions ...es/references/adr/2026-08-05-document-generation-v1-to-v2-migration-strategy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,8 +60,7 @@ document stays usable in v1 surfaces after the flag is switched off whenever at

The read path for v1 auto-generates missing media for non-static documents. For documents that already carry `document_file`
rows, it skips this and fails gracefully instead. Otherwise, switching back would produce a divergent v1 rendering from the
nearly empty v2 `document.config`. This guard is the single deliberate exception to v1 taking no dependency on v2 and will
be removed alongside v1.
nearly empty v2 `document.config`. This guard prevents v1 from regenerating v2 documents and will be removed alongside v1.

#### Legacy Zugferd types

Expand All @@ -81,9 +80,8 @@ The v2 admin API routes are available regardless of the flag state. The flag onl
Entry points for v2 are annotated `@experimental stableVersion:v6.8.0 feature:DOCUMENT_GENERATION_REWORK` and may change
until v2 becomes the default in 6.8.

For customer-facing downloads, the storefront and Store API routes gain a flag-gated branch. This branch resolves files
through the new document file structure first before falling back to legacy media fields. The URLs do not change and the
routes survive the removal of v1 in 6.9.
For customer-facing downloads, the storefront and Store API routes keep their URLs and resolve persisted files through the
shared compatibility read path. The routes survive the removal of v1 in 6.9.

### Public Extension Surface

Expand Down