urnetwork/build v2026.9.13-1045655440

on GitHub

Changes in v2026.9.13-1045655440

v2026.9.13-1045587450 ... v2026.9.13-1045655440 -- 9 commits across 5 components.

linux

urnetwork/linux dffb9c9bb...b4690297a

• Use Noble zxing package in Linux CI (b4690297a)

build

urnetwork/build 8a258d2af...9e51dfa54

• Use Noble zxing package for Linux GUI (9e51dfa54)

connect

urnetwork/connect 92aa7e4e9...d0cad77c6

• bringyour.yml: document the whole device association shape (cf3978d23)
  The server's spec conformance test reported four implementation fields the spec did not carry, all on GET /device/associations: client_id and network_name on pending_adoption_devices, and duration_minutes on both shared lists.
• bringyour.yml: leave the competition api to sn/api/competition.yml (d3e96f9f6)
  The ten /competition/* routes were dual-listed here and there. That document is the competition's own and the fuller one, and the routes are a separate security domain with their own opaque role-scoped tokens, so listing them in two places only invites the two from drifting apart. Removed the paths, the nineteen Competition* schemas, the competition tag and the CompetitionBearerAuth scheme, and left a pointer in the info description.
• api/check-routes.sh: fail when the spec and the route table disagree (4975576fd)
  Takes a server checkout, extracts every router.NewRoute registration the api service serves (api/api.go plus the oauth routes it appends), extracts every method and path bringyour.yml documents, normalizes the regex captures and the {name} parameters into the same shape, and exits non-zero when either side has something the other does not. zsh, grep, sed, sort and comm only, so it needs neither a yaml parser nor the go toolchain.
• bringyour.yml: document every registered route, and correct the drifted ones (c5b7ba9e8)
  The spec covered 128 of the api service's 192 route registrations. The 64 it did not are now in: the static redirects and /status, the sim-latency competition, /stats/providers-map and the two legacy stats aliases, /auth/wallet-nonce, /network/remove-clients, /network/extender-activate, the provider probe control plane, the store and processor notifications, the client purchase-verify pair, x402, the subnet artifact/evidence/client-key surfaces, /verify/stats and /verify/proofs, the ...

warp

urnetwork/warp 51d96dbb5...33810fb24

• Pin privacy-safe Mimir rejection classification boundaries (33810fb24)
• Checkpoint privacy-safe Mimir rejection diagnostics (03d4e5ed5)

server

urnetwork/server 55232eb41...10e8a7e40

• api: normalize regex-escaped dots when comparing routes to the spec (a22629ffa)
  The route table registers the oauth discovery paths as regexes, so their literal dots are escaped (/.well-known/jwks.json). normalizePath trimmed the anchors and rewrote capture groups but left the escapes in place, so the now-documented /.well-known/* spec paths matched no route and TestSpecRoutesImplemented failed. Unescape . alongside the other rewrites; escaped dots are the only regex escape the route table uses.

Filtered out of this changelog: 2 merge commits (both sides are already listed), 1 version-stamp commit written by all/run.sh on every release. Re-run all/changelog.py --from v2026.9.13-1045587450 --to v2026.9.13-1045655440 --filters= to include them.