revert: remove Docker Hub integration from release workflow and README

Restores release workflow to ghcr.io-only publishing. Removes Docker Pulls badge from README. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
ci: add Docker Hub dual-push and pulls badge to README
2026-06-10 03:28:58 +00:00 · 2026-03-28 19:34:29 -04:00 · 2026-03-28 19:24:12 -04:00 · 2026-03-28 18:09:41 -04:00
2 changed files with 3 additions and 1 deletions
@@ -39,6 +39,8 @@ certctl is a self-hosted platform that automates the entire certificate lifecycl
 | [Connectors](docs/connectors.md) | Build custom issuer, target, and notifier connectors |
 | [Compliance Mapping](docs/compliance.md) | SOC 2 Type II, PCI-DSS 4.0, NIST SP 800-57 alignment guides |

+> **Next release:** v2.1.0 will be tagged after the full V2 feature suite passes manual QA across all 34 sections of the [testing guide](docs/testing-guide.md). Automated CI (1,471 Go tests + 193 frontend tests) gates every commit; the manual playbook covers integration, deployment, and UX verification that unit tests can't reach.
+
 ## Why certctl Exists

 Certificate lifecycle tooling today falls into two camps: expensive enterprise platforms (Venafi, Keyfactor, Sectigo) that cost six figures and take months to deploy, or single-purpose tools (cert-manager, certbot) that handle one slice of the problem. If you run a mixed infrastructure — some NGINX, some Apache, a few HAProxy nodes, maybe an F5 — and you need to manage certificates from multiple CAs, there's nothing self-hosted that covers the full lifecycle without vendor lock-in.
@@ -5071,7 +5071,7 @@ openssl crl -in /tmp/subca-crl.der -inform DER -noout -issuer

 ## Release Sign-Off

-All 34 parts must pass before tagging v2.0.7.
+All 34 parts must pass before tagging v2.1.0.

 | Section | Pass? | Tester | Date | Notes |
 |---------|-------|--------|------|-------|