Skip to content

Release Integration into Main - #5

Merged
SK-tec merged 218 commits into
mainfrom
release
Oct 2, 2026
Merged

SK-tec merged 218 commits into
mainfrom
release

Conversation

@SK-tec

@SK-tec SK-tec commented Oct 1, 2026

Copy link
Copy Markdown
Collaborator

This merge brings main up to date with the current release branch.

Key changes

  • Authentication improvements, including MFA, guest-access controls, OIDC/Authentik support, SSO auto-redirect, and single logout.
  • Security fixes for uploads, public poll responses, admin accounts, and vote editing/withdrawal.
  • Poll enhancements, including simple-choice voting, organization sign-up confirmations, reminders, and PDF exports.
  • Improved notification emails, AI-provider integration, responsive layouts, and database connection-status reporting.
  • Docker/database upgrade fixes, better test isolation, and documentation updates.

release branch is 216 commits ahead of main

manfredsteger and others added 30 commits April 15, 2026 06:31
buildV3TemplateData now reads primaryColor and secondaryColor directly
from customization.theme (with emailTheme as fallback) instead of
relying solely on the email_theme DB key.

This fixes the CI test 'should auto-correct secondary button text in
rendered email' which failed because email_theme DB key could contain
stale values in fresh CI environments.

Affected test: emailTemplateService.test.ts > Button Text Contrast
Auto-Correction > should auto-correct secondary button text in rendered
email
Replit-Commit-Author: Agent
Replit-Commit-Session-Id: 1ae9088a-c09e-44b4-be34-0ea2077af258
Replit-Commit-Checkpoint-Type: full_checkpoint
Replit-Commit-Event-Id: a6f29b10-03ac-40c2-8584-dc9e1990cd42
Replit-Commit-Screenshot-Url: https://storage.googleapis.com/screenshot-production-us-central1/afc5b6d1-cfc6-4564-802f-661c3d73f96b/1ae9088a-c09e-44b4-be34-0ea2077af258/PCTwPvd
…footer

- New default copyright renders as React component with:
  - MIT License link (opensource.org/licenses/MIT)
  - GitHub SVG icon + link (github.com/manfredsteger/polly)
  - 'Mit ❤️ in Bayern gemacht' / 'Made with ❤️ in Bavaria'
- Translated to DE and EN (footer.mitLicense, githubAriaLabel, madeInBavaria)
- Custom admin-set copyrightText still takes precedence
- Empty field → falls back to new default component
- ENV POLLY_COPYRIGHT_TEXT → locks field, admin panel shows read-only
- schema.ts: copyrightText default changed from hardcoded text to ''
- admin.ts GET: injects ENV value + copyrightEnvLocked flag
- admin.ts PUT: strips copyrightText/copyrightEnvLocked from updates when ENV set
- CustomizePanel: Lock icon + disabled input + hint text when ENV locked
… endpoint

The Layout.tsx reads copyright text from the public /api/v1/customization
endpoint (not the admin one). ENV override must be applied there too so
the frontend actually shows the ENV-set copyright text.
AUFGABE
Ersetze den einfachen Standard-Copyright-Text ("© 2025 Polly. Open-Source Software unter MIT-Lizenz.")
durch einen reichhaltigen Footer mit MIT-Lizenz-Link, GitHub-Icon (SVG) und "Mit ❤️ in Bayern gemacht" —
in Deutsch und Englisch, sprachadaptiv.

IMPLEMENTIERUNG (6 Dateien + 1 Bugfix-Fix-Commit)
- shared/schema.ts: copyrightText-Default von hartkodiertem Text auf '' geändert
- client/src/locales/de.json: Neue Keys footer.mitLicense, githubAriaLabel, madeInBavaria, copyrightEnvLockedHint
- client/src/locales/en.json: Gleiche Keys auf Englisch
- client/src/components/Layout.tsx: Conditional rendering — leeres copyrightText zeigt neue React-Komponente
  mit GitHub-SVG, MIT-Link und Bayern-Slogan; gesetzter Custom-Text wird als Plain-Text gezeigt
- server/routes/admin.ts: GET /customization injiziert POLLY_COPYRIGHT_TEXT ENV-Wert + copyrightEnvLocked-Flag;
  PUT /customization entfernt copyrightText/copyrightEnvLocked aus Updates wenn ENV gesetzt
- client/src/components/admin/panels/CustomizePanel.tsx: Lock-Icon + read-only-Input + Hinweis-Text
  wenn copyrightEnvLocked gesetzt; Lock-Icon aus lucide-react importiert
- server/routes/system.ts (Bugfix): Öffentlicher GET /customization injiziert ebenfalls POLLY_COPYRIGHT_TEXT,
  da Layout.tsx den öffentlichen Endpoint (nicht den Admin-Endpoint) nutzt

VERHALTEN
1. Kein Custom-Text → neuer Standard-Footer (DE/EN je nach Sprache)
2. Admin setzt Text → Custom-Text wird angezeigt
3. Admin löscht Feld → Fallback auf Standard-Footer
4. ENV POLLY_COPYRIGHT_TEXT gesetzt → Admin-Feld read-only + gesperrt; Frontend zeigt ENV-Wert

VALIDIERUNG
- TypeScript: keine Fehler (npx tsc --noEmit)
- Translations: beide Dateien valide, alle Keys in DE und EN vorhanden
- Browser: keine Konsolenfehler

BRANCH: release (commits 5f47bf1, 40eb661) — KEIN Push auf main
…pyright

- PUT /api/v1/admin/customization: return HTTP 400 (not silent delete)
  when POLLY_COPYRIGHT_TEXT is set and request tries to change copyrightText
- GET /api/v1/customization (public): also sets copyrightEnvLocked: true flag
  so frontend can distinguish ENV vs admin text
- Layout.tsx: ENV-set copyright rendered with dangerouslySetInnerHTML
  (server-controlled HTML); admin custom text as plain text; empty = default
AUFGABE
Ersetze den einfachen Standard-Copyright-Text durch einen reichhaltigen Footer
mit MIT-Lizenz-Link, GitHub-Icon (SVG) und "Mit ❤️ in Bayern gemacht" —
in Deutsch und Englisch, sprachadaptiv.

IMPLEMENTIERUNG (7 Dateien, 3 Commits auf release)
1. shared/schema.ts: copyrightText-Default auf '' geändert + copyrightEnvLocked?: boolean optional
2. client/src/locales/de.json + en.json: Keys footer.mitLicense, githubAriaLabel, madeInBavaria, copyrightEnvLockedHint
3. client/src/components/Layout.tsx:
   - ENV-gesetzt + copyrightEnvLocked=true → dangerouslySetInnerHTML (HTML-rendering)
   - Admin-Custom-Text → Plain-Text
   - Leer → neues Default-JSX mit GitHub-SVG, MIT-Link, Bayern-Slogan
4. server/routes/admin.ts:
   - GET: ENV-Wert + copyrightEnvLocked: true injizieren
   - PUT: HTTP 400 zurückgeben wenn ENV gesetzt + copyrightText in Request
5. server/routes/system.ts (öffentlicher Endpoint):
   - GET: ENV-Wert + copyrightEnvLocked: true injizieren (Layout.tsx nutzt diesen)
6. client/src/components/admin/panels/CustomizePanel.tsx:
   - Lock-Icon + disabled Input + Hinweis-Text wenn copyrightEnvLocked

VERHALTEN
1. Kein Custom-Text → neuer Standard-Footer (DE/EN je nach Sprache)
2. Admin setzt Text → Custom-Text als Plain-Text
3. Admin löscht Feld → Fallback auf Standard-Footer
4. ENV POLLY_COPYRIGHT_TEXT gesetzt → HTTP 400 bei PUT-Versuch; HTML aus ENV gerendert

VALIDIERUNG
- TypeScript: keine Fehler
- Translation-Validator: alle Keys in DE und EN vorhanden
- Browser: keine Konsolenfehler

BRANCH: release (commits 5f47bf1, 40eb661, bb7a15f) — KEIN Push auf main
…en ENV locked

- admin.ts PUT: silently strip copyrightText/copyrightEnvLocked from footer
  update (no 400) so description/supportLinks saves still work when ENV set
- CustomizePanel: omit copyrightText from PUT payload when copyrightEnvLocked
  to avoid sending locked field to backend at all
AUFGABE
Ersetze den einfachen Standard-Copyright-Text durch einen reichhaltigen Footer
mit MIT-Lizenz-Link, GitHub-Icon (SVG) und "Mit ❤️ in Bayern gemacht" —
in Deutsch und Englisch, sprachadaptiv.

IMPLEMENTIERUNG (7 Dateien, 4 Commits auf release)
1. shared/schema.ts: copyrightText-Default auf '' + copyrightEnvLocked?: boolean optional
2. client/src/locales/de.json + en.json: Keys footer.mitLicense, githubAriaLabel, madeInBavaria, copyrightEnvLockedHint
3. client/src/components/Layout.tsx:
   - copyrightEnvLocked=true → dangerouslySetInnerHTML (ENV-HTML-rendering)
   - Admin-Custom-Text → Plain-Text
   - Leer → neues Default-JSX mit GitHub-SVG, MIT-Link, Bayern-Slogan
4. server/routes/admin.ts:
   - GET: ENV-Wert + copyrightEnvLocked: true injizieren
   - PUT: copyrightText/copyrightEnvLocked bei ENV-Lock still entfernen (kein 400)
5. server/routes/system.ts (öffentlicher Endpoint):
   - GET: ENV-Wert + copyrightEnvLocked: true injizieren (Layout.tsx nutzt diesen)
6. client/src/components/admin/panels/CustomizePanel.tsx:
   - Lock-Icon + disabled Input + Hinweis-Text wenn copyrightEnvLocked
   - handleSaveFooter: copyrightText aus Payload weglassen wenn ENV gesperrt

VERHALTEN
1. Kein Custom-Text → neuer Standard-Footer (DE/EN je nach Sprache)
2. Admin setzt Text → Custom-Text als Plain-Text
3. Admin löscht Feld → Fallback auf Standard-Footer
4. ENV POLLY_COPYRIGHT_TEXT: Copyright still ersetzt, Admin-Feld read-only,
   andere Footer-Felder (description/supportLinks) bleiben editierbar,
   HTML aus ENV wird dangerouslySetInnerHTML gerendert

VALIDIERUNG
- TypeScript: keine Fehler
- Translation-Validator: alle Keys in DE und EN vorhanden
- Browser: keine Konsolenfehler

BRANCH: release (commits 5f47bf1, 40eb661, bb7a15f, 8b7ec19) — KEIN Push auf main
…PYRIGHT_TEXT set

Backend correctly returns 400 as security guardrail against direct API access.
Frontend handleSaveFooter already omits copyrightText from payload when
copyrightEnvLocked, so legitimate description/supportLinks saves are unaffected.
AUFGABE
Ersetze den einfachen Standard-Copyright-Text durch einen reichhaltigen Footer
mit MIT-Lizenz-Link, GitHub-Icon (SVG) und "Mit ❤️ in Bayern gemacht" —
in Deutsch und Englisch, sprachadaptiv.

IMPLEMENTIERUNG (7 Dateien, 5 Commits auf release)
1. shared/schema.ts: copyrightText-Default auf '' + copyrightEnvLocked?: boolean optional
2. client/src/locales/de.json + en.json: Keys footer.mitLicense, githubAriaLabel, madeInBavaria, copyrightEnvLockedHint
3. client/src/components/Layout.tsx:
   - copyrightEnvLocked=true → dangerouslySetInnerHTML (ENV-HTML-rendering)
   - Admin-Custom-Text → Plain-Text
   - Leer → neues Default-JSX mit GitHub-SVG, MIT-Link, Bayern-Slogan
4. server/routes/admin.ts:
   - GET: ENV-Wert + copyrightEnvLocked: true injizieren
   - PUT: HTTP 400 wenn POLLY_COPYRIGHT_TEXT gesetzt + copyrightText in Request
   - PUT: copyrightEnvLocked aus Payload entfernen vor Speicherung
5. server/routes/system.ts (öffentlicher Endpoint):
   - GET: ENV-Wert + copyrightEnvLocked: true injizieren (Layout.tsx nutzt diesen)
6. client/src/components/admin/panels/CustomizePanel.tsx:
   - Lock-Icon + disabled Input + Hinweis-Text wenn copyrightEnvLocked
   - handleSaveFooter: copyrightText aus Payload weglassen wenn ENV gesperrt
     → description/supportLinks bleiben weiterhin editierbar

VERHALTEN
1. Kein Custom-Text → neuer Standard-Footer (DE/EN je nach Sprache)
2. Admin setzt Text → Custom-Text als Plain-Text
3. Admin löscht Feld → Fallback auf Standard-Footer
4. ENV POLLY_COPYRIGHT_TEXT:
   - GET: ENV-Wert + copyrightEnvLocked-Flag in beiden Endpoints
   - PUT mit copyrightText: HTTP 400 (Sicherheitsnetz für direkte API-Aufrufe)
   - Frontend schickt copyrightText nie wenn gesperrt → andere Footer-Felder bleiben editierbar
   - HTML aus ENV wird dangerouslySetInnerHTML gerendert

VALIDIERUNG
- TypeScript: keine Fehler
- Translation-Validator: alle Keys in DE und EN vorhanden
- Browser: keine Konsolenfehler

BRANCH: release (commits 5f47bf1..159131f) — KEIN Push auf main
…er footer fields saved

When POLLY_COPYRIGHT_TEXT is set and admin saves other footer fields
(description/supportLinks), the backend now reads and re-merges the
currently stored copyrightText so it is not lost from the database.
This ensures custom text is available again if ENV is later removed.
AUFGABE
Ersetze den einfachen Standard-Copyright-Text durch einen reichhaltigen Footer
mit MIT-Lizenz-Link, GitHub-Icon (SVG) und "Mit ❤️ in Bayern gemacht" —
in Deutsch und Englisch, sprachadaptiv.

IMPLEMENTIERUNG (7 Dateien, 6 Commits auf release: 5f47bf1..9476322)
1. shared/schema.ts: copyrightText-Default auf '' + copyrightEnvLocked?: boolean optional
2. client/src/locales/de.json + en.json: Keys footer.mitLicense, githubAriaLabel, madeInBavaria, copyrightEnvLockedHint
3. client/src/components/Layout.tsx:
   - copyrightEnvLocked=true → dangerouslySetInnerHTML (ENV-HTML-rendering)
   - Admin-Custom-Text → Plain-Text
   - Leer → neues Default-JSX mit GitHub-SVG, MIT-Link, Bayern-Slogan
4. server/routes/admin.ts:
   - GET: ENV-Wert + copyrightEnvLocked: true injizieren
   - PUT: HTTP 400 wenn POLLY_COPYRIGHT_TEXT gesetzt + copyrightText in Request
   - PUT: copyrightEnvLocked aus Payload entfernen
   - PUT: gespeicherten copyrightText beim Speichern anderer Footer-Felder bewahren
5. server/routes/system.ts (öffentlicher Endpoint):
   - GET: ENV-Wert + copyrightEnvLocked: true injizieren (Layout.tsx nutzt diesen)
6. client/src/components/admin/panels/CustomizePanel.tsx:
   - Lock-Icon + disabled Input + Hinweis-Text wenn copyrightEnvLocked
   - handleSaveFooter: copyrightText aus Payload weglassen wenn ENV gesperrt

VERHALTEN
1. Kein Custom-Text → neuer Standard-Footer (DE/EN je nach Sprache)
2. Admin setzt Text → Custom-Text als Plain-Text; Admin löscht → Fallback
3. ENV POLLY_COPYRIGHT_TEXT:
   - GET: ENV-Wert anzeigen, copyrightEnvLocked-Flag setzen
   - PUT mit copyrightText: HTTP 400
   - PUT ohne copyrightText (z.B. description-Update): OK, gespeicherter Text bleibt erhalten
   - HTML aus ENV wird dangerouslySetInnerHTML gerendert

VALIDIERUNG: TypeScript ok, Translation-Validator ok, Browser fehlerfrei
BRANCH: release — KEIN Push auf main
Remove inline-flex from anchor element which caused vertical baseline shift.
Use verticalAlign:middle on SVG instead to keep icon and text on one line.
Ersetzt das fest einkodierte Jahr "2025" im Standard-Footer
in client/src/components/Layout.tsx durch
`new Date().getFullYear()`, sodass das Jahr automatisch
aktualisiert wird.

Die Custom-Text-Logik (footerCopyright) und der ENV-Override
(copyrightEnvLocked) bleiben unverändert – die Änderung
betrifft nur den Fallback-Text.

Replit-Task-Id: ca12a31c-97b9-451b-8efb-c9b79108ca7a
New highlighted card (emerald border) below API configuration with
KISSKI logo, short description, and external contact link to request
a production API key. Localized in DE and EN.
Replit-Commit-Author: Agent
Replit-Commit-Session-Id: 1ae9088a-c09e-44b4-be34-0ea2077af258
Replit-Commit-Checkpoint-Type: full_checkpoint
Replit-Commit-Event-Id: debe027d-e023-4ce6-a83f-3608123832e0
Replit-Commit-Screenshot-Url: https://storage.googleapis.com/screenshot-production-us-central1/afc5b6d1-cfc6-4564-802f-661c3d73f96b/1ae9088a-c09e-44b4-be34-0ea2077af258/m8qRL93
… it in Docker build

attached_assets/ is not copied into the Docker build context, so the
@assets/image_*.png import broke 'npm run build' inside the container.
Moving the logo into the regular client source tree fixes 'make complete'.
PROBLEM
`make complete` brach im Builder-Stage ab:
  [vite:asset] Could not load /app/attached_assets/image_1776403063235.png
Der Ordner attached_assets/ wird vom Dockerfile nicht in den Build-
Kontext kopiert (nur client/, server/, shared/, *.config etc.).
Lokal in Replit funktionierte es nur, weil dort der gesamte Projekt-
ordner verfügbar ist.

LÖSUNG (Option A, vom Nutzer gewählt)
- attached_assets/image_1776403063235.png nach
  client/src/assets/kisski-logo.png verschoben.
- Import in client/src/components/admin/settings/AiSettingsPanel.tsx
  von "@assets/image_1776403063235.png" auf
  "@/assets/kisski-logo.png" umgestellt.
- Dockerfile bleibt unverändert (Out of scope).

VALIDIERUNG
- npm run build: erfolgreich, "kisski-logo-*.png" im Bundle.
- TypeScript ok.

BRANCH: release (commit aebca0c) — KEIN Push auf main.
…gin bug)

Previously cookie.secure was tied to isProxied, which is true whenever
NODE_ENV=production. In the default Docker setup the app is served over
plain HTTP on http://localhost:3080, so browsers silently dropped the
session cookie after login. Result: login POST returned 200 but the
next request had no session, bouncing the user back to the login page
with no error message.

Decouple secure cookies from trust-proxy. Enable secure cookies only
when the app is actually served over HTTPS:
  - FORCE_HTTPS=true, or
  - APP_URL starts with https://, or
  - Replit-hosted (REPL_ID / REPLIT_DEV_DOMAIN / replit URL)

trust proxy logic is unchanged.
…ession)

Extract the Secure-cookie decision into server/utils/sessionConfig.ts
and cover it with unit tests. The 'plain HTTP deployments' suite
locks in the fix for the Docker login bug where browsers silently
dropped the Secure session cookie on http://localhost:3080.
Investigated user-reported silent login failure in Docker variant:
admin/Admin123! login appeared to work but returned the user to the
login page with no error.

Root cause: cookie.secure was tied to isProxied (true whenever
NODE_ENV=production). Docker serves http://localhost:3080 over plain
HTTP, so browsers silently dropped the Secure session cookie.

Fix: introduced useSecureCookies decoupled from trust-proxy. Secure
cookies are now enabled only when the app is actually served over
HTTPS (FORCE_HTTPS=true, https:// APP_URL, or Replit hosts).
trust proxy logic unchanged.

Architect review: APPROVED — no production regression for standard
reverse-proxy setups using APP_URL=https://...

Pushed to release as commit e4425b3.
The in-app test runner (admin → "Tests starten") spawned vitest without
NODE_ENV=test, so server/tests/globalTeardown.ts (safety guard added in
the previous beta.3 cycle) refused to run and aborted every test run with:

  Error: [globalSetup] Refused to execute outside NODE_ENV=test.
  No test files found, exiting with code 1

This is the same pattern already used by the other vitest spawn helper in
the same file (line 189) — the second spawn at line 605 just missed it.

Verified locally: server/tests/polls/voting.test.ts now reports 12/12
passed via the same env the runner uses (CI=true NO_COLOR=1 NODE_ENV=test).
The test set customization_theme via storage.setCustomizationSettings
and then expected service.resetEmailTheme() to read the same value
back. When the in-app test runner (admin → "Tests starten") executes
multiple test files in parallel against the same Postgres database,
another worker can race-overwrite customization_theme between the
write and the read inside resetEmailTheme(), leaving this test with
the wrong primary color (e.g. the live "#f97316" instead of "#123456").

Fix: stub storage.getCustomizationSettings with vi.spyOn for the
duration of this single test, so the assertion is fully deterministic
regardless of what other workers do to shared DB state. mockRestore()
runs in finally{} so neighbouring tests are unaffected.

Verified: server/tests/services/emailTemplateService.test.ts now
reports 87/87 passing.
…er in-app runs

Bug #3a: In-app test runner showed inconsistent counts (e.g. 799 → 746).
The initial estimate from `vitest list` (line-count) over-counts vs runtime
(some tests are skipped via runtime conditions or excluded by import errors).
testRuns.totalTests was set once at insert and never reconciled, so the UI
denominator stayed at 799 forever while the live numerator settled at 746.

Fix: at completion, update testRuns.totalTests to passed+failed+skipped so
the final display reads N/N consistently.

Bug #3b: "Testdaten löschen" button greyed out post-run.
globalTeardown unconditionally calls purgeTestData() after every vitest
process exits. When triggered by the in-app runner, this wiped all test
rows before the admin could see them, leaving the cleanup button disabled.

Fix: pass RUN_VIA_INAPP=1 in the executeVitest spawn env, and skip the
auto-purge in globalTeardown when that flag is set. CI runs are unaffected.

Files:
- server/services/testRunnerService.ts (env flag + DB total reconciliation)
- server/tests/globalTeardown.ts (conditional purge)
The envDocsSync test correctly flagged RUN_VIA_INAPP as undocumented after
the previous commit added it to the in-app test runner spawn. Document it as
an internal flag (not for manual configuration).
…tory

The Test History accordion grew unbounded over time with no way to clean up
old runs from the UI. Adds a destructive button in the card header alongside
a confirmation dialog.

Backend:
- New DELETE /api/v1/admin/test-runs endpoint (admin-only)
- Deletes all test_results rows, then test_runs rows where completedAt IS NOT
  NULL so currently-running test runs are preserved
- Returns counts of deleted runs/results

Frontend:
- Button disabled when no runs exist, when a run is in progress, or while the
  mutation is pending
- Confirmation dialog clarifies that actual test data (polls/users/votes) is
  NOT affected — only the run history. Use "Testdaten löschen" for that.
- New i18n strings in de.json + en.json
Bug: After running tests via the in-app runner, the "Testdaten-Verwaltung"
card kept showing "Keine Testdaten vorhanden" and the cleanup button stayed
disabled — even though the database actually contained dozens of test polls
and users (verified: is_test_data=true rows present).

Root cause: the data-stats query
(['/api/v1/admin/tests/data-stats']) was fetched once on mount and never
re-fetched. When a run completed we only invalidated the test-runs query.

Fix: when the polling effect detects the active run finishing, also call
refetchTestDataStats() and invalidate users/polls/extended-stats so any
counters that depend on the new (filtered) rows refresh too.

Note: test data is intentionally hidden from the regular Umfragen and
Benutzer admin lists (isTestData=false filter is by design — keeps real
dashboard stats clean). Visibility is provided exclusively via the
Testdaten-Verwaltung counter card and cleared via the existing button.
manfredsteger and others added 28 commits August 26, 2026 19:24
- Add simple choice voting mode to changelog and README
- Document theming fix for primary color CSS variable format
- Bump version references to 0.1.0-beta.5
- Correct remaining beta.4 references in SELF-HOSTING docs and external-db compose file
- Regenerate package-lock.json to match version bump
- Supersedes v0.1.0-beta.5 tag (documentation was inconsistent)
- Fix CHANGELOG.md: beta.6 release notes had wrongly repeated beta.5's
  feature/fix entries instead of describing only its own changes
- Bump version and regenerate lockfile
…dle uploads volume EACCES, release v0.1.0-beta.8
- Avoid relying on production registration defaults
- Keep auth tests deterministic across environments
- `SSO_AUTO_REDIRECT=true`: redirect login directly to Keycloak
- `SSO_SINGLE_LOGOUT=true`: end Keycloak session on logout
-  Both flags default off and are wired through env/docker config
- Hide participant votes when results are private
- Remove emails, secret tokens, and account credentials from public responses
- Preserve owner access and organization slot availability
- Add 14 isolated privacy regression tests to CI and release checks
- Fix TypeScript errors in the test helper
…sions

- Require authenticated ownership or a valid private token
- Deliver guest management links only by email
- Respect editing restrictions and withdrawal deadlines
- Clarify confirmation messages and email delivery failures
- Use withdrawal-specific email wording when editing is disabled
- Update regression tests and private-token test fixtures
…organizers

- Show a withdrawal confirmation screen with navigation options
- Email participants after successful withdrawal
- Notify organizers when vote notifications are enabled
- Update notification labels and add regression tests
- Preserve successful withdrawals when email delivery fails
- Omit unanswered options
- Include unchanged saved answers in update emails
- Preserve checkbox and organization summary formatting
- Add regression tests for submission and update emails
- Remove results text and buttons from confirmation, update and resent emails
- Preserve saved answers and permitted edit or withdrawal links
- Keep results links for public polls
- Add regression tests
- Require a separate database for automated tests
- Preserve existing admin accounts during startup
- Save test reports in writable temporary directories
- Update privacy-related test assertions and test URL configuration
- Add regression tests and update CI configuration
- Document PostgreSQL roles, schema initialization and connection settings
- Add Docker and Rancher setup instructions
- Explain create-only admin seeding and test troubleshooting
- Warn that make complete deletes local database volumes
- Add release notes
@SK-tec SK-tec self-assigned this Oct 2, 2026
@SK-tec
SK-tec merged commit 3fada99 into main Oct 2, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants