Tags give the ability to mark specific points in history as being important
-
v0.11.1
21ac809c · ·v0.11.1 - Fixed `pr0xteus upgrade` so it refreshes the installed command before starting the selected release. Upgrades now apply current Tailscale routes and proxy-address wiring without a separate `setup` or `start` command. - Added wrapper-upgrade regression coverage for tagged and rolling releases, user and system installs, and failed command refreshes.
-
v0.11.0
9065de3a · ·v0.11.0 Breaking before 1.0: `POST /v1/proxies` no longer returns a top-level `url`. Read `proxies.socks5` instead. The response now also includes `proxies.http`, an authenticated HTTP forward-proxy URL for the same lease, cell, credentials, expiry, and egress IP. - Added the controller HTTP proxy on port 8080. It supports HTTP requests and HTTPS `CONNECT` tunnels, with all traffic routed through the selected cell. It strips proxy credentials and hop-by-hop headers before forwarding. - Fixed the controller SOCKS relay so domain-form requests retain their target hostname instead of being forwarded as `0.0.0.0`. Failures now produce safe, structured logs without exposing lease credentials or destinations. - Added HTTP proxy host-port and public-address settings, including Tailscale Serve wiring. The default remains loopback-only at `127.0.0.1:8080`. - Expanded control API, real-provider, installed-stack, proxy protocol, and configuration tests. The 90% coverage gate now includes the HTTP proxy. - Removed stale comments from the pipeline configuration.
-
v0.10.6
baad2269 · ·Updates the Servicepack framework to v1.9.2 and drops the removed `make audit` target. - Updated Servicepack from v1.9.1 to v1.9.2, which removes the framework's `make audit` target. `make sec` already runs `govulncheck` (with semgrep, merged into `sec.sarif`), so the standalone vulnerability target was redundant. - Removed the `make audit` line from the README target list and the development docs. `make audit-compose` (Compose safety checks) is unchanged.
-
v0.10.5
f25bb806 · ·v0.10.5: fix the badges coverage-artifact name so CI goes green Fixes the badges job, the last thing keeping CI red. - The v0.10.3 migration set the code job's coverage_artifact to coverage-percent.txt, but the badges job downloads the coverage artifact under its default name coverage. The two never matched, so once the code job went green (v0.10.4) the badges job failed with "Artifact not found for name: coverage". Removed the explicit coverage_artifact so the code job and the badges job both use the shared coverage default. coverage-percent.txt stays the file name inside the artifact.
-
v0.10.4
d4f8f514 · ·v0.10.4: fix CI by unwiring the test-lifecycle from the Testcontainers targets Fixes CI, which had been red since v0.10.2. - The v0.10.2 test-lifecycle wrapper started the installer dev-stack (make restart) before every make test* target, including the make test-coverage that CI runs. That stack needs wireguard secrets CI does not have, so its config check failed and the whole run went red. Removed the wrapper from the Testcontainers targets (make test, make test-unit, make test-integration, make test-coverage, make test-api, make test-real); they stand up their own containers and need no local stack, which is what lets CI run them. make test-installed, which drives the live installer stack, keeps the reset/start/stop lifecycle and stays a local-only target.
-
v0.10.3
e757a7f4 · ·v0.10.3: servicepack v1.9.1 + code-workflow CI migration with make sec Development and CI tooling only. No change to the pr0xteus controller or proxy behavior. - Updated the servicepack framework from v1.6.4 to v1.9.1: the testcontainers integration harness now runs on the host network so sibling containers' published ports are reachable, framework files re-sort their imports after a module rename, a make sec target is available (govulncheck + semgrep), and make servicepack-update itself is hardened (a git-defined backup that does not choke on a dev stack's root-owned files, and a guard that fails the update if a downstream .gitignore would silently drop a synced framework file). - Migrated CI from the Go-specific go-workflow to the generic code-workflow. It runs make lint, make test-coverage, make sec, and make generate (codegen-drift gate) in the dev image, uploads the coverage percentage for the badge, and posts the security SARIF to the Security tab. The image build, badges, and ClawHub publish now depend on this code job. - Added semgrep to the dev image so make sec runs, and marked two false-positive math/rand findings (upstream selection and retry-backoff jitter, neither needs crypto entropy) with a bare // nosemgrep.
-
v0.10.2
6e67fb3b · ·v0.10.2: make test targets own the local stack lifecycle - Every make test* target now owns the local stack lifecycle: it resets and starts the installer-equivalent development stack before its suite and stops it on success, failure, or interruption, through the new scripts/test-local-lifecycle.sh wrapper. Tests no longer need a manual make run beforehand and never leave the local Compose project running. test-installed no longer depends on the run target; the wrapper handles startup and teardown.
-
-
-
-
-
-
-
-
-
-
-
-
-