v2.56.1 (nothing moves while a page loads, every text readable in both themes, and a DNS account without credentials is never used to issue)
A patch release. It adds no feature and the API contract stays at 2.65. Most of it comes from one complaint, that the certificate list jumped when it opened: a browser test that holds every API answer until the page has painted found 24 movements across the interface, and a UI audit after it found what is below. Every fix but one has a test that was run before the change and failed; the one is the height of the activity rows, which was measured.
-
Fix: a DNS account with no credentials is never used to issue (#1476, closes #1469). A new instance writes its first settings with sixteen DNS providers in the old single-account format, every credential empty, and the migration to multi-account turns each into an account named
defaultand makes it the default. The settings page therefore showed all sixteen as "Configured, 1 accounts" with nothing filled in, and the create form offered the empty account. Issuance used it too: when asked for by name, and as the default even next to an account of the same provider that had credentials. Its blank token went into certbot's credentials file, so the error came from the DNS provider. Now:- issuance skips an account without its provider's required fields. Asked for by name, it stops with "account '...' not configured" before certbot runs; as the default, it gives way to the first account that has credentials;
- the settings page shows "Configured", and the number of accounts, from the server's own check. An empty account carries a "No credentials" badge;
- the create form offers only accounts that can issue.
What changes for you: a certificate whose DNS account has no credentials now fails at once with that message, instead of failing at the DNS provider. Route53 through the host's AWS credentials keeps working with
auth_mode: iam_role, as documented, andCLOUDFLARE_TOKENkeeps filling the default Cloudflare account. The empty accounts stay in the settings: they hold nothing, and editing one is a way to fill in credentials. -
Fix: nothing on screen moves while a page loads (#1470). Opening the certificate list, the top bar went to two lines for a moment and the page dropped 40 px; the table headers slid sideways; the footer jumped out of the middle of the screen; each row's Deployment chips shrank and grew back. Most pages had some of this. Each case is fixed where it starts, and
tests/test_ui_nothing_on_screen_moves_while_a_page_loads.pyholds them: it fails if anything watched moves after the first paint, with the answers, and Alpine, arriving after it. On a first visit over a slow link, the fonts still arrive after the first paint and move text by a few pixels. -
Fix: the dashboard's counts agree with its rows (#1473). The Valid counter and the Valid filter still used "more than 30 days left" after #1429 moved Expiring to the renewal rule. A 47-day certificate with 20 days left had a green Valid badge and was in no counter, and one due for renewal with more than 30 days left was counted twice. They now follow the rule the rows follow.
-
Fix: an empty client list offers the first certificate (#1473). It opens with the "Active" chip pressed, so with no client certificate at all it said that no certificate matched the filter, and the button that creates one never appeared.
-
Accessibility: every text is readable in both themes (#1474, #1475). Measured on 20 views:
- in dark mode the brand blue as text was 2.5 to 2.7:1 (help links, the active settings item, pressed chips);
- muted text was 4.4:1 on the light grey surfaces and 4.0:1 on dark inputs;
- fixed
gray-400text was 2.5:1 in about fifty places; - two yellow buttons were 2.9:1 with white text;
- 57 icon-only controls, the shortcuts button on every page among them, were under 3:1.
Every visible text now reaches 4.5:1 and every icon-only control 3:1, on every view and in both themes;
tests/test_ui_text_is_readable.pyholds it. The rate limits of Settings > API Keys are dimmed while rate limiting is off, and are not held to it, as WCAG does not hold inactive controls. -
Layout (#1470):
- every settings tab starts at the same height (the content jumped up to 32 px on a switch);
- no page is wider than a 360 or 390 px phone (the inventory was 590 px, and five settings tabs were wider too);
- "New" is whole on a 360 px phone;
- activity rows are 84 px instead of 108;
- the new-certificate drawer's Server/Client switch no longer moves under the pointer. The Server line now reads "TLS certificate from your CA, validated over DNS or HTTP".
-
Dependencies: the image ships
soupsieve4.1.1 andopentelemetry-api1.45.2 (#1472). They were outside GHSA-6655-6qjp-jx7x, GHSA-mmhr-3c5m-f64f and GHSA-7g44-g9rc-x53w (soupsieve 2.10) and GHSA-mf5v-w3w3-f6cg (opentelemetry-api 1.45.1). None of them was reachable: soupsieve is BeautifulSoup's CSS selector engine, and the three DNS providers that use BeautifulSoup never call a selector.