tilo/emails
Watch
5
0
Fork
You've already forked emails
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Reconcile native subjects after copy-only edits #1

Merged
qwolff merged 1 commit from feat/native-subject-sync into main 2026-10-25 23:13:21 +00:00
Conversation 0 Commits 1 Files changed 4 +59 -1
qwolff commented 2026-10-25 23:13:20 +00:00
Owner
Copy link

Authentik hashes blueprint bytes, not the environment resolved by !Env. A subject-only content edit must therefore change a discovered blueprint too. Emit a small literal-subject blueprint for the two existing EmailStages; it changes no tokens, expiry, flows or users. Both values still derive from the same JSON copy as the ConfigMap.

55 tests and the generated-drift check pass, including a real temporary-source edit proving both artifacts change. Native offline rendering remains green. The deployment projects this alongside the existing contributor blueprints.

Authentik hashes blueprint bytes, not the environment resolved by !Env. A subject-only content edit must therefore change a discovered blueprint too. Emit a small literal-subject blueprint for the two existing EmailStages; it changes no tokens, expiry, flows or users. Both values still derive from the same JSON copy as the ConfigMap. 55 tests and the generated-drift check pass, including a real temporary-source edit proving both artifacts change. Native offline rendering remains green. The deployment projects this alongside the existing contributor blueprints.
fix: reconcile native subjects after copy-only email updates
Some checks failed
Email design / validate (pull_request) Successful in 27s
Details
Email design / native (pull_request) Failing after 1m7s
Details
602568f54c
qwolff merged commit b69ccc1740 into main 2026-10-25 23:13:21 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
tilo/emails!1
No description provided.