Skip to content

Add 1.7.0 release notes - #443

Merged
drudge merged 1 commit into
mainfrom
claude/project-thread-1m25fo
Oct 13, 2026
Merged

drudge merged 1 commit into
mainfrom
claude/project-thread-1m25fo

Conversation

@drudge

@drudge drudge commented Oct 13, 2026

Copy link
Copy Markdown
Owner

Requested by Nick · project thread

Before: CHANGELOG.md has notes for 1.6.2-beta.1 and 1.7.0-beta.1 through beta.17, but no 1.7.0 section, so the Release workflow would refuse to publish 1.7.0. The docs still say they cover 1.6.1. The earlier draft (#407) stopped at beta.8, before per-device blocking and schedules.

After: one 1.7.0 section written for someone upgrading from 1.6.x, grouped by what they'll notice: per-device blocking (rule sets, app blocking, holds, schedules, query log Block/Allow for a rule set), block list correctness, DNSSEC fixes, DNS hardening, Insights row hide, console shape refresh and phone/Safari fixes, Dynamic DNS outage summaries, new MCP tools, process metrics, and the Go security bump. Upgrading from 1.6.x folds in every beta's upgrade notes, including the bypass_clients → No Blocking migration, upgrading cluster nodes together, and new MCP tools staying off when [mcp] tools is set. Beta-only regressions and internal refactors are left out.

How: started from #407's text for betas 1 to 8 and added betas 9 to 17. Docs move to 1.7.0 (navigation.json, docs/index.md, Technitium guide) so go test ./docs passes; the screenshot caption stays 1.6.1 until the website release workflow retakes them. Dated 2026-10-13; adjust if the release slips.

Supersedes #407.


Generated by Claude Code

@drudge drudge self-assigned this Oct 13, 2026
@drudge
drudge merged commit fff4cd9 into main Oct 13, 2026
4 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.

1 participant