v1.7.1-rc.4

Full Changelog: v1.7.1-rc.3...v1.7.1-rc.4

[1.7.1-rc.4] — 2026-10-31

This is the fourth release candidate for the 1.7.1 maintenance release. It includes all rc.3 changes, fixes four dependency advisories and backports environment redaction for the 1.7 JSON store. It is opt-in testing: v1.7.0 remains the stable release, and latest and the 1.7 channel do not move. This candidate starts a new seven-day soak at publication.

Security

• Redact environment values whose names match the secret patterns, and URLs carrying credentials, before writing containers or update-operation snapshots to Loki JSON. Startup scrubs those fields in the existing store and saves the repair before serving requests (#1523). This is pattern-based redaction: values under unrecognised names can still be stored in plaintext. Copies and backups made before this upgrade are not scrubbed.
• Environment reveal now inspects the exact live Docker container locally or through its owning agent. Upgrade traditional agents alongside the controller; older agents and edge connections return an explicit unsupported response instead of revealing cached values. Changes only to recognised secret values no longer count as runtime-detail changes.
• Update joi to 18.3.1 and follow-redirects to 1.16.2, and override minimatch and glob to their fixed majors in backend, UI and E2E tooling. This clears GHSA-4528-x5fx-h6hg, GHSA-mrwp-f3q8-3g9p, GHSA-g3hv-75wg-m249 and GHSA-3g3m-2fjr-6pw4 on the 1.7 maintenance line.

Changed

• CI jobs now pin step-security/harden-runner v2.22.3 (from v2.21.1). On GitHub's westus2 hosted runners a DNS change made block-mode egress drop connections to allowed hosts, including the runner's own calls to github.com, so jobs finished every step and then sat until their timeout (step-security/harden-runner#708).

Note: this is a maintenance cut, built from dev/v1.7 at 2b351e6ec041688af418635ddb91de0ae5620682, not from main.

• The container image and release artifact are cosign-signed (identity release-cut.yml@refs/heads/main, since the workflow run itself always executes at that ref), but carry no SLSA build-provenance attestation — this workflow's own OIDC token always claims main HEAD as the build source, which would be false for this artifact, so attestation is skipped rather than publish a false claim.