66 Commits

Include renames

Author	SHA1	Message	Date
justme	806493567b	ci: share Linux restore artifacts before builds [CI]	2026-10-21 13:31:07 +08:00
justme	a6f9759238	ci: build musl only for arm64 and reuse toolchain cache [CI]	2026-10-21 12:41:58 +08:00
justme	490b008a57	scripts: unify Linux native builds and retain restore caches [CI] ... Build musl and glibc for amd64 and arm64 through one native package path. Reuse musl outputs for OCI images and OpenWrt installers, and export binaries inside a rootless unshare session. Restore the executable dependency graph into a shared persistent NuGet cache, build managed dependencies once, and run isolated native publishes in parallel. Clean temporary outputs and expired image layers under store locks, retire inactive legacy stores after seven days, and retain two toolchain exports. Add regression coverage for staging, extraction, packaging and cleanup boundaries.	2026-10-21 12:29:00 +08:00
justme	4515d7b075	scripts: publish unified Agent artifacts and restore CI coverage [CI] ... Remove Probe build jobs and release paths. Transfer Gitea publishing credentials to both Agent architecture jobs, publish each platform archive once, and run slow tests after development images are published.	2026-10-21 11:56:06 +08:00
justme	cd193378a6	probe: add native OpenWrt deployment and signed automatic updates [CI]	2026-10-20 14:15:01 +08:00
justme	24ba05fbb6	perf(ci): pin staged restore mtimes so the restore layer caches, drop build intermediates from the layer [CI]	2026-10-19 14:05:22 +08:00
justme	5c00ec434e	fix(ci): read the commit status from the public Gitea address [CI]	2026-10-19 14:03:46 +08:00
justme	1ccbb847b5	ci: build the dev images in parallel with the checks and gate only the push [CI]	2026-10-19 13:58:21 +08:00
justme	fb9dc155f5	fix(ci): avoid leaking cache lock to MSBuild nodes [CI]	2026-10-19 11:15:19 +08:00
justme	b9ec6d80b0	fix(quic): merge static MsQuic support with latest main [CI]	2026-10-11 01:05:21 +08:00
justme	a44895d860	fix(quic): statically link MsQuic for Alpine nodes [CI]	2026-10-11 01:00:37 +08:00
justme	d7b48c068c	ci: speed up backend build and parallelize image publishing [CI]	2026-10-10 07:29:11 -07:00
justme	04f116e092	ci: clean up backend test processes on cancel [CI]	2026-10-10 06:48:20 -07:00
justme	b46ba69aa0	ci: raise Buildah nofile limit for Zig AOT [CI]	2026-10-10 06:09:17 -07:00
justme	15f159ab39	ci: raise WSL runner PID budget for NativeAOT [CI]	2026-10-10 06:03:44 -07:00
justme	a77f12545b	ci: initialize isolated Buildah auth files [CI]	2026-10-10 05:51:13 -07:00
justme	9919de53d3	ci: keep WSL agent online for pipelines [CI]	2026-10-10 05:48:48 -07:00
justme	1975253beb	ci: bake cached toolchain into Podman agent and fix nested Buildah [CI]	2026-10-10 05:44:21 -07:00
justme	2e1dbcf4ce	ci: use cache path for NuGet scratch [CI]	2026-10-10 04:40:09 -07:00
justme	a1101424d2	ci: add .NET 10 NativeAOT AotAnywhere builder [CI]	2026-10-10 04:36:47 -07:00
justme	a1b8af8509	ci: bound and cancel Buildah commands [CI] [SKIP TESTS] ... Signed-off-by: JustMe <mr.toing@outlook.com>	2026-10-10 17:30:55 +08:00
justme	a3b9671d62	ci: rotate Buildah storage after cache mount failure [CI] [SKIP TESTS] ... Signed-off-by: JustMe <mr.toing@outlook.com>	2026-10-10 16:43:42 +08:00
justme	da353d239a	ci: isolate caches and trust ARM Alpine keys [CI] [SKIP TESTS] ... Signed-off-by: JustMe <mr.toing@outlook.com>	2026-10-10 15:51:10 +08:00
justme	49812e94c0	ci: cross-build dev images with AotAnywhere [CI] [SKIP TESTS] ... Signed-off-by: JustMe <mr.toing@outlook.com>	2026-10-10 15:45:45 +08:00
justme	376020fe34	fix(ci): isolate per-arch node build workspaces [CI] [SKIP TESTS]	2026-10-10 15:27:55 +08:00
justme	8b3abd5b22	feat(ci): publish ARM64 development node images [CI] [SKIP TESTS]	2026-10-10 15:19:30 +08:00
justme	238046d959	test(backend): parallelize isolated fixtures [CI] [SKIP TESTS]	2026-10-10 04:54:18 +08:00
justme	77d8404f59	ci(test): load MsQuic for Linux tests [CI]	2026-10-10 04:11:55 +08:00
justme	29d998bc94	build(quic): bundle Linux runtime libraries [CI]	2026-10-10 04:01:24 +08:00
justme	2d31bd091e	ci: gate on the fast tests (about 20s); slow end-to-end tests run in parallel with the image build [CI]	2026-10-09 14:33:03 +08:00
justme	c9c21f8056	ci: fix the failed-test retry (wildcard filter, ignore zero-test exit code, two attempts) [CI]	2026-10-09 14:09:54 +08:00
justme	b2b63c065d	ci: sync packaging and docs into the test cache; retry failed tests once [CI]	2026-10-09 14:02:42 +08:00
justme	be04045c8c	ci: incremental backend tests, cached web dependencies, web build in parallel with the tests	2026-10-09 13:39:55 +08:00
justme	a9f78f99df	ci: version from the tag or the commits since it; dev images from main gated on tests; recognise -dev. tags [CI SKIP]	2026-10-09 13:20:30 +08:00
justme	535bb3517d	feat: node updates by restart, auto by default; Podman Quadlet install from the panel alongside compose [CI]	2026-10-09 01:33:22 +08:00
justme	12be44645f	feat: install nodes and the backend from a static compose file; remove dead code [CI] ... Agent, Probe and Backend now start from one static compose.yaml plus a local .env: the panel (or the release assets, for the very first Backend) provides the file, the panel's command writes the public values into .env, checks the file's SHA-256 and runs compose up. Updating is compose pull && compose up -d. The image is chosen by the CI channel (:latest, or MOSHIRO_VERSION in .env), not by the panel; the previous one-line script stays as a fallback. - packaging/compose/{agent,probe,backend}/compose.yaml are the single source, embedded in the Backend and served at /install/compose/{file}; the root compose.yaml moved there. Releases also carry them and list them in the signed SHA256SUMS. - The container entrypoint defaults the node name to the host name. - Join token creation returns a compose block (.env, url, hash, per-platform commands); the admin dialog leads with it. - Remove code with no references (HotLayer members, LiveHub.SubscriberCount, QueryService.ParseParams, ReleaseService.Forget, a few constants) and reduce the install-code lookup to the role it is for.	2026-10-08 20:24:23 +08:00
justme	904ea2b0ae	refactor: remove the runtime binary binding; every release registration path verifies the CI signature [CI] ... The hash a node reports about itself cannot be trusted (a swapped binary can copy the old hash), so the runtime binding only caught files that were replaced by something that did not lie. Provenance stays where it can be verified: the signed release manifest (digest) and the signed SHA256SUMS. - Remove BinaryBindingService, the node_bindings table (schema v15 drops it), BinaryPolicy, the handshake hash/manifest fields and the admin binary column. - Drop the per-platform "binaries" list from the release manifest, the hash scripts and the updater's installed.manifest copy. - ReleaseService.PublishAsync now verifies the release signature, so the admin POST /releases route is no longer an unsigned path; tests sign with a test key. - Docs: section 16 explains why the runtime check is gone.	2026-10-08 18:30:05 +08:00
justme	a4f3d1892a	ci: all-platform node binaries in the signed release manifest; signed SHA256SUMS for the archives; web build once before the parallel backend builds; release 0.3.3 [CI SKIP]	2026-10-08 16:26:29 +08:00
justme	cd9e677331	fix(ci): build the web apps once before the two backend architectures; release 0.3.1 [CI]	2026-10-08 16:05:38 +08:00
justme	879d1c8593	fix: installer checks containers only; the panel reads signed manifests from the registry when it has none; unsigned-updater nodes are labeled from the panel's manifests; sign node release images; release 0.3.0 [CI]	2026-10-08 15:59:28 +08:00
justme	0b384a58f5	fix: hash the node binary without the registry auth file that does not exist yet [CI]	2026-10-08 05:43:51 +08:00
justme	4841f7b15b	feat: bind each node to the binary it runs at its first handshake; refuse changes that are not in a CI-signed manifest [CI]	2026-10-08 05:39:13 +08:00
justme	117d34a2af	feat: signed manifests live in the image registry; updaters and first deploys fetch and verify them without the panel [CI]	2026-10-08 05:05:13 +08:00
justme	f704c66dd9	feat: CI registers release manifests without a token; the panel verifies the CI signature instead [CI]	2026-10-08 04:22:01 +08:00
justme	fbda9487d5	feat: serve the web apps from the Backend (embedded, allow-listed, no filesystem access) so passkeys bind to the panel's own domain [CI]	2026-10-08 04:09:40 +08:00
justme	a2f88a344b	feat!: genesis-pinned operator set, server identity with an encrypted control link, key-less join codes; release key continuity ... Join codes need no passkey touch and carry only public values (genesis fingerprint, owner credentials, installer hashes). Nodes pin the genesis and owners at enrollment and only follow passkey-signed operator set versions. The panel's server key is listed in the set; pinned nodes require its signature and run the control link under AES-256-GCM. Password sessions carry no capabilities. The updater adopts a next_key from a signed manifest. Bump version to 0.2.0. [CI SKIP]	2026-10-08 03:21:44 +08:00
justme	af2962fc58	feat: one-line install for agents and probes from one shared script (curl | bash, zsh, PowerShell) [CI]	2026-10-07 20:02:38 +08:00
justme	a9f562441f	feat!: probes generate their own keys and enroll with a join token; node and peer keys are separate [CI]	2026-10-07 16:57:34 +08:00
justme	33b9782a1d	ci: tolerate legacy Backend release webhook [CI]	2026-10-07 13:00:35 +08:00
justme	84f9d211bc	backend: require confirmation for signed channel updates [CI]	2026-10-07 12:57:20 +08:00