CertLord v1.0.1

CertLord 1.0.1

This maintenance release bounds combined command stdout/stderr to 4 MiB and
raises an explicit failure when output exceeds that budget. Truncated command
output is never accepted as a successful receipt. Cleanup also bounds discarded
output so a noisy child cannot extend termination indefinitely.

Process selector initialization now occurs before launch. Launch or pipe
registration failures close owned resources and terminate/reap a started child.
The existing deployment retry policy remains unchanged: remote jobs still need
idempotent behavior, and local process cleanup does not prove a remote effect
was cancelled.

Install with python -m pip install --upgrade 'certlord==1.0.1', or use
decryptus/certlord:1.0.1 with the current Compose guide.

CertLord 1.0.0

First stable release — 8 October 2026. Promotes the qualified rc2 feature set
without adding runtime features. The supported topology uses one active lifecycle
daemon; the operating limits below remain part of the release contract.

Included

• ACME HTTP-01 issuance and renewal through Certbot and ACME HTTP Connector.
• External PEM import with certificate/key checks and explicit versioned replacement.
• Vault KV v2 storage and separate API/Vault authentication responsibilities.
• Authenticated HTTP administration, CLI commands and an explicitly selected TUI.
• Redis work tracking, deployment leases, retries and bounded worker shutdown.
• Auton deployment, optional confirmed remote receipts and destination TLS checks.
• Authenticated certificate/worker observations and Prometheus metrics.
• Optional read-only Textual browser: install certlord[textual] and run
  certlord tui --ui textual.

Installation and supported scope

Python 3.11/3.12 on POSIX; Debian packaging targets Debian 12 / amd64. Provision
Vault, Redis and Auton separately. Use one active lifecycle daemon and idempotent
deployment jobs. See installation,
configuration and operations and installation evaluation.

Install the exact stable version:

python -m pip install 'certlord==1.0.0'

Limits

There is no exactly-once remote execution guarantee. A remote job can survive a
local timeout or expired lease, and a later attempt can resubmit work. Confirmed
receipts do not provide durable recovery of every uncertain job. Optional TLS
verification covers one configured destination per certificate.

Rehearse backup restoration, credential rotation and uncertain-job recovery on
your deployment. Disposable CI does not establish production readiness, saturation
capacity or long-duration stability. Live monitoring providers and additional
platforms require separate qualification. No automatic production deployment is
performed by publishing this release.

CertLord v1.0.0

CertLord 1.0.0

First stable release — 8 October 2026. Promotes the qualified rc2 feature set
without adding runtime features. The supported topology uses one active lifecycle
daemon; the operating limits below remain part of the release contract.

Included

• ACME HTTP-01 issuance and renewal through Certbot and ACME HTTP Connector.
• External PEM import with certificate/key checks and explicit versioned replacement.
• Vault KV v2 storage and separate API/Vault authentication responsibilities.
• Authenticated HTTP administration, CLI commands and an explicitly selected TUI.
• Redis work tracking, deployment leases, retries and bounded worker shutdown.
• Auton deployment, optional confirmed remote receipts and destination TLS checks.
• Authenticated certificate/worker observations and Prometheus metrics.
• Optional read-only Textual browser: install certlord[textual] and run
  certlord tui --ui textual.

Installation and supported scope

Python 3.11/3.12 on POSIX; Debian packaging targets Debian 12 / amd64. Provision
Vault, Redis and Auton separately. Use one active lifecycle daemon and idempotent
deployment jobs. See installation,
configuration and operations and installation evaluation.

Install the exact stable version:

python -m pip install 'certlord==1.0.0'

Limits

There is no exactly-once remote execution guarantee. A remote job can survive a
local timeout or expired lease, and a later attempt can resubmit work. Confirmed
receipts do not provide durable recovery of every uncertain job. Optional TLS
verification covers one configured destination per certificate.

Rehearse backup restoration, credential rotation and uncertain-job recovery on
your deployment. Disposable CI does not establish production readiness, saturation
capacity or long-duration stability. Live monitoring providers and additional
platforms require separate qualification. No automatic production deployment is
performed by publishing this release.

CertLord v1.0.0rc1

CertLord 1.0.0rc1

Release candidate prepared on 2026-10-03. This is not the final 1.0.0 release.

Included

• ACME HTTP-01 issuance and renewal through Certbot and ACME HTTP Connector.
• External PEM import with certificate/key checks and explicit versioned replacement.
• Vault KV v2 storage and separate API/Vault authentication responsibilities.
• Authenticated HTTP administration, CLI commands and an explicitly selected TUI.
• Redis work tracking, deployment leases, retries and bounded worker shutdown.
• Auton deployment, optional confirmed remote receipts and destination TLS checks.
• Authenticated certificate/worker observations and Prometheus metrics.

Evaluation

Python 3.11/3.12 on POSIX; Debian packaging targets Debian 12 / amd64. Provision
Vault, Redis and Auton separately. Use one active lifecycle daemon and idempotent
deployment jobs. See installation,
configuration and operations and testing.

After the candidate is published, install its exact version in an isolated environment:

python -m pip install 'certlord==1.0.0rc1'

Limits

There is no exactly-once remote execution guarantee. A remote job can survive a
local timeout or expired lease, and a later attempt can resubmit work. Confirmed
receipts do not provide durable recovery of every uncertain job. Optional TLS
verification covers one configured destination per certificate.

Rehearse backup restoration, credential rotation and uncertain-job recovery on
your deployment. Disposable CI does not establish production readiness, saturation
capacity or long-duration stability. Live monitoring providers and additional
platforms require separate qualification. No automatic production deployment is
performed by publishing this candidate.