Repository navigation
Releases: cryptolabsza/cryptolabs-proxy
Release list
1.5.4 — Managed support adverts
Adds visible CryptoLabs managed support adverts to the Fleet login screen and landing page. Both link to https://cryptolabs.co.za, and the dashboard footer includes an explicit support link.
Verified with 930 regression tests passing (2 existing skips), focused login/setup/error-state tests, desktop/mobile previews, independent code review, and required release builds.
CryptoLabs Proxy 1.5.3
Fix selected-update capability detection when the proxy Python package is shipped under /app/src. The nested probe now declares that source path inside the inspected running proxy container. Existing capability validation and source-identity guards are preserved.
Source: fe8978e6e9f4eaf3586914b498f6f85f308091e5.
Published immutable linux/amd64 image: ghcr.io/cryptolabsza/cryptolabs-proxy@sha256:ba6e766d75e820097ba7869f80c8f791e6788285bcfa99be058ef76213e007ec.
Authentication and persistent-data behavior are unchanged. Broad image alias promotion is held; use the numeric version or exact digest for this release.
CryptoLabs Proxy 1.5.2
Fix native configuration adoption incorrectly reporting runtime drift when Docker returns identical mounts in a different order. All mount details, credentials, runtime settings and other ordered values remain protected by the existing identity checks.
The compatible host CLI can deploy the already approved immutable proxy image 1.5.1; its authentication module is unchanged. Validation: the regression reproduced the failure before the fix; 52 deployment tests and 924 regression tests passed (2 existing skips). Both independent reviews found no open issues.
CryptoLabs Proxy 1.5.1
Fleet Manager now shows Latest only after a successful, recent channel comparison, including for pinned services. Outdated or unverifiable services show their actual status, and long build hashes are shortened to eight characters so service cards stay within the screen.
This patch release also includes the password-form fixes and configuration-preservation improvements in PR #7. Native configuration adoption preserves the site's routes, certificates, persistent account store and service runtimes during a proxy-only update.
Validation: 917 regression tests passed (2 skipped), 162 release-focused tests passed, and 29 CI contract tests passed. Required release-PR builds must pass before merge. Numeric artifacts are published first; shared image aliases are promoted separately after customer deployment verification.
cryptolabs-proxy 1.5.0
Adds two optional customer configuration policies for primary-host requests and HTTP-to-HTTPS handling, including ACME routing. Adoption preserves the declared TLS health command and validates it before repeat setup; omitted policies retain existing behavior.
Validation: 877 source tests passed, 2 skipped; 128 release metadata and publication controls passed, 1 skipped. Independent command-validation and API reviews are clear for the frozen source. Auth source is unchanged.
Numeric release availability only. Native customer/site acceptance and deployment alias promotion remain pending.
CryptoLabs Proxy 1.4.0
Controller configuration adoption now coordinates with ordinary proxy-managed updates through a durable guard on the existing authentication volume. Incomplete or interrupted adoption keeps updates held until matching verified recovery completes.
- Add the additive controller-adoption capability and explicit guarded completion API.
- Preserve marker custody across helper exit, crash and expired leases.
- Bind guard RPC transport to the configured Docker Engine socket and validate helper identity and bounded responses.
Validation: 762 source tests pass, with two declared exclusions; independent transport and recovery checks pass. Release/version contracts are checked separately on the signed merge. Actual Linux serving-artifact and customer acceptance remain pending.
Numeric publication preserves GitHub Latest and broad image aliases. Guard coverage applies to the supported updater/adoption interfaces; external lifecycle owners require declared maintenance coordination.
v1.3.1
CryptoLabs Proxy 1.3.1 corrects the shared self-hosted runner temporary-directory collision that stopped the 1.3.0 Python build before publication. Build and publish jobs now allocate separate temporary directories, preserve the original retained artifact bundle for recovery, and retain verified publication receipts after a later reporting failure.
Validation: 46 focused workflow/publication tests passed; independent adversarial checks covered concurrent jobs, stale state, allocation failures, retained-bundle recovery and receipt retention. Application behavior is unchanged from 1.3.0.
Packages and images will be verified through the normal release workflows before standard-customer deployment validation. Suite compatibility, fresh customer installation and both dogfood deployments remain under verification; deployment aliases and GitHub Latest will be promoted after those checks.
cryptolabs-proxy 1.3.0
Adds supported host configuration planning and adoption for existing proxy installations, including declared hostname forwarding and TLS routes. Adoption validates existing configuration and preserves identity storage, roles, signing material, certificates and service routes.
Selected updates check the running updater's capabilities before creating a job or launching its helper. Proxy replacement uses the host adoption workflow, with guarded preparation and recovery. The installed host package validates identity data without importing server-only authentication dependencies.
Validation: 715 source tests passed, with two skips. Independent dispatch checks covered the original old-updater failure and supported current dispatch; clean installed-package checks passed. Publication receipts, actual customer adoption and both dogfood deployments remain separate acceptance gates. Deployment image aliases remain held pending those gates.