Dawnline 0.20.0
Build packages / CI (push) Blocked by required conditions
Build packages / Version (push) Waiting to run
CI / Web (format, types, tests, bundles) (push) Blocked by required conditions
CI / ShellCheck (push) Blocked by required conditions
CI / Backend (Go: vet, tests, a real ubusd and uhttpd) (push) Blocked by required conditions
CI / Package files (push) Blocked by required conditions

- **Backend rewritten in Go.** One daemon, `dawnlined`, replaces the whole ucode backend: the rpcd plugin, the agent, the CLI and the updater. The package no longer depends on ucode.
- **Per-architecture builds.** The release carries the backend for arm64, ARMv7, mips, mipsle and amd64; the router fetches its own after the package is installed and checks its sha256. Dawnline does not run on other architectures (older ARM, 32-bit x86, RISC-V).
- **Faster on the router.** A firewall sync takes 0.06 s instead of 0.9 s; a full apply takes about 300 ms. The portal is served by the daemon itself, without a CGI process per request.
- **Live pages.** The admin and the portal follow a live stream from the router instead of re-fetching the whole state every 30 seconds.
- **Admin redesigned in the portal's style.** Three sections (Overview · Log · Settings); a server is a page of its own with People, Places and Settings; a device opens as a dialog over its person.
- **Changes wait for «Apply».** Every setting, and a person's access, is staged in one dock before it reaches the router.
- **Configuration rollout.** After a change that makes devices fetch their configuration again, the admin shows how many have fetched it and who has not. Every setting shows beforehand (⟳N) how many devices it will touch.
- **Waiting for a decision.** Overview and People put first the people who need one (access ended, limit reached, a device that does not connect), each with its one action a tap away.
- **Bulk actions on people.** «Select» (or a long press on a card) picks several people to extend by a month, pause or resume at once.
- **Undo.** An action done from a card or a request is undone from its toast.
- **Update dialogs redesigned.** An update is one view from its question to its result; Dawnline's own update runs in it like every other, and the page reloads itself once the new version answers. Other versions are a list, each with its notes and Install on a page of its own.
- **Site to site: networks behind a router.** A router connected as a device can have networks behind it (up to eight, /16 to /30): the server routes them and applies the router's access to them. A network that shares addresses with a tunnel, the router's own networks or another site is refused by name.
- **Routers from the portal.** People can add a router and name its networks on their own page; the admin accepts or declines with a reason, or lets them through without asking.
- **Check access and Health know the networks behind routers.**
- **Usage limits reworked.** A monthly limit no longer follows the calendar. A person's month starts with their first traffic and ends a month later; the next one starts only when they connect again, so time away uses up none of it. Before, everyone's limit reset on the 1st.
- Extra data lasts until that person's month ends; «Reset usage» starts the month anew.
- A limit is for a month or for the whole term; the admin and the portal show when it resets.
- Charts that said «this month» show the last 30 days.
- After the update nobody loses what was counted: the month that was running becomes the person's first and ends on the 1st.
- **Access by time of day removed.** The Hours limit is gone from the admin, the portal and the backend; saved hours are dropped.
- **Expiry simplified.** An end date always stops access, with a heads-up three days before; the per-person choice is gone.
- **No false disconnects from sleeping phones.** A phone or a tablet stays online through ten minutes of silence.
- **Mobile Safari fixes.** Pressing a control no longer sends the page to its top; tab tracks that do not fit scroll; switches animate after a press.
This commit is contained in:
Aemeath committed 2026-11-13 09:43:50 +03:00
1 parent f8130e39a8
commit ac90575b0b
788 files changed
+139244 -41720

No files matched your search

+19
View File
@@ -0,0 +1,19 @@
# Release notes: how the list of changes is collected
A release's `- ` points (`AGENTS.md` › Releases) and any list of «what changed» asked for along the way are collected the same way. The owner set it on 2026-11-12, after a list made from commit messages came out long, mixed trivia with what matters and missed whole features: «в будущем мне нужно чтобы ты так всегда логи собирал».
## The rule
- **From the code, against production.** Production is the last release: the tip of `origin/main`, the last tag `vX.Y.Z`. Go through the difference itself (`git diff vX.Y.Z..HEAD`), not only the commits' titles and bodies: the backend's methods that came and went (`backend/methods`), the settings (`backend/model`), the admin's pages, flows and widgets (`web/src/admin`), the portal (`web/src/portal`), the package's dependencies, the scripts. The commit messages are where to start, never the source: the list made from them alone missed bulk actions on people, the rollout of a new configuration, «Waiting for a decision», Undo and the simplified expiry.
- **Key changes only.** What somebody who runs Dawnline wants to know: what was rebuilt (the backend in Go), what is faster and by how much, what can be done now that could not, what is gone, what behaves differently. One short line each, the thing first.
- **Not the trivia.** The owner's own examples of what does not belong: «Show speeds in bytes per second (KB/s, MB/s), the measure the traffic beside them is counted in» («околобесполезная инфа») and «New README screenshots of the redesigned admin» («юзелесс»). A unit, a label, a picture, a move of code nobody sees: left out.
- **A rework is told whole.** What it was, what it is now, and what happens to what people had before the update. One line for the limits counted by a person's own month was not enough (the owner: «а как же реворк системы юседжа и времени старта отсчета»): it takes the rule (the month begins with their first traffic, the next only when they connect again), what follows from it (extra data, «Reset usage», the charts) and what an update does to the month that was running.
- **A number says where it is from.** Measured for this list, or taken from `docs/` or a commit's message (and on which router). Nothing is called checked that was only read in the code.
- **In English.** The points are English whatever language they were asked for in: what the owner writes in Russian is what he means, not how to write it («то что я пишу на русском это то что я имею ввиду а не как написать»). The talk around the list stays in his language.
## How
1. Find production: `git fetch`, then the default branch's tip and its tag.
2. Size the difference by area (`git diff --numstat`), then read each area for what came, went and changed: names that exist on one side only are the quickest lead (methods, options, files added and deleted), and each lead is checked in the code before it is written down, since a thing drawn again is not a thing added.
3. Read the commits' bodies for the reasons and the measurements.
4. Write the short list; expand the reworks; say what was left out on purpose only if asked.