Repository navigation
Changes since v1.20.1.
1.20.11 — Multiple daily schedule windows
- Add up to 32 independent day/time windows to blocklists, whitelists, and policy targets with a shared timezone and OR matching.
- Preserve existing single-window schedules through SQLite/MySQL schema upgrades.
- Add window controls, per-window day presets, complete summaries, and next-transition calculations across overlapping and overnight windows.
- Validate every saved window and cover weekday/weekend boundaries, DST, round trips, and migration.
1.20.10 — Apply target precedence to scoped lists
- Use only the highest-priority scheduled target’s list assignments instead of combining endpoint, hostname, and network assignments.
- Preserve global lists, whitelist-target bypass, and fallback outside target schedules.
- Keep Policy Tester list explanations consistent with the decision engine and document the precedence change.
1.20.9 — Flush PTR cache
- Add an authenticated, CSRF-protected PTR cache flush control in Settings → Runtime.
- Clear learned identities and cached answers, queue tracked clients for fresh resolution, and preserve query history.
- Discard stale in-flight results and serialize invalidation with policy reloads.
1.20.8 — Compact policy target search
- Keep Search and Reset sized to their content and aligned with the target filters, with wrapping on narrow screens.
1.20.7 — Compact policy target actions
- Shorten policy target action labels to Pause, Resume, and Edit.
- Restore pause/resume controls on whitelist targets using the existing target-state action.
1.20.6 — Clear policy target terminology and polished controls
- Distinguish blocklist targets from whitelist targets in cards, editors, schedules, and creation buttons.
- Hide blocking state and pause/resume controls for whitelist targets, whose bypass follows their schedule independently of blocking state.
- Polish policy target actions with consistent sizing, icons, theme-aware colors, responsive layouts, and keyboard focus states.
1.20.5 — Streamlined README
- Focus the README on a concise overview, one complete recommended setup, and the stable-main update procedure.
- Move optional tag installation and checkout-transition instructions into the alternative-installation guide; consolidate setup and navigation text.
- Preserve every Reddit review and attribution unchanged as the final README section.
1.20.4 — Stable main installation workflow
- Recommend standard clone and fast-forward pull on stable main, keeping exact release-tag installation as an option.
- Add safe instructions for moving an existing single-branch tag checkout to main; retain matching release configuration for pinned Docker Hub images.
- Document dev as the home for unreleased application changes and main for stable code and current documentation, including contributor instructions.
1.20.3 — Pin installation instructions to the stable release
- Use the current published v1.20.1 tag in both source-build and Docker Hub configuration clone instructions.
- Replace branch-pull upgrade instructions with explicit tag fetch/checkouts and explain detached HEAD behavior and matching Docker image versions.
- Clarify the distinction between current source and published release versions; keep release-maintenance guidance consistent.
1.20.2 — Documentation consolidation
- Keep the recommended source-built Compose quick start in the README and move detailed deployment, user, API, operations, and contributor material into linked guides.
- Correct ignored-question semantics, system-theme options, incremental PTR reconciliation, and statistics/retention guidance; clarify migration prerequisites and runtime authentication.
- Consolidate repeated setup, security, and release instructions, and replace the completed TLS implementation checklist with links to current documentation.
- Update Docker Hub examples to the successfully published 1.20.1 image.
- Preserve all Reddit reviews unchanged as the final README section. Existing release tags and branches remain unchanged.
Upgrade note: Scoped lists now follow endpoint → hostname → network priority instead of combining assignments. Global lists still apply. Existing schedules are preserved; database upgrades add support for additional time windows.