Dates on which something you run changes, loses its fixes or becomes a legal duty, whether or not you upgrade anything. Each with what it affects, a check to run and the source that sets it.
29 dates · every one read from its source on 22 October 2026
On this page · 9 sections
The short answer
Three kinds of date matter. Certificate lifetimes shrink every year until 2029, so renewal has to be automatic and watched. End-of-life dates for Kubernetes, Node.js, Python, PostgreSQL and Linux distributions mean no more security fixes after the day. And the EU Cyber Resilience Act turns vulnerability reporting and software bills of materials into obligations for anyone selling software in the EU.
None of these show up as an error on the day. A certificate fails weeks later, at its first short renewal; an unsupported version keeps running until its next vulnerability. Run the checks below now, while you can still choose when to act.
This page is rebuilt every few hours, so “passed” and “coming” follow today’s date. Managed services keep their own calendars: where a provider’s date differs from the project’s, the provider’s is the one that applies to you.
GitHub moves ubuntu-latest to the Ubuntu 26.04 image between 19 October 2026 and 19 November 2026, bringing Docker 29, Compose 5, Helm 4 and Python 3.14 into jobs that never asked for them.
Affects: Every workflow with runs-on: ubuntu-latest.
At the end of extended support, EKS upgrades the cluster automatically to the oldest version still in extended support. A cluster upgraded this way cannot be rolled back.
Affects: EKS clusters on 1.31.
Check
aws eks describe-cluster --name my-cluster --query cluster.version --output text
What to do: Upgrade on your own schedule before the date, after checking for removed APIs and changed defaults.
The default (classic) profile issues 64-day certificates with a 10-day authorization reuse period. Existing certificates change at their next renewal after the date.
Affects: Every site on Let's Encrypt: renewal has to keep working, more often.
Check
systemctl list-timers '*certbot*' # when renewal last ran, and runs next
What to do: Confirm renewal is automated and monitored; a renewal that silently fails now takes the site down sooner.
The maximum validity for certificates from publicly trusted authorities drops to 100 days.
Affects: Anyone renewing certificates by hand, or on a schedule tuned to longer lifetimes.
Check
# When the certificate a site is serving expires
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -enddate
What to do: Renewal must be automatic, and alert someone when it fails.
Including a software bill of materials "in a commonly used and machine-readable format covering at the very least the top-level dependencies" (Annex I, Part II).
Affects: Manufacturers placing products with digital elements on the EU market.
What to do: Generate SBOMs from the built artifact, keep them by digest, and make sure you can query them.
The final step of the schedule: certificates from publicly trusted authorities may be valid for at most 47 days.
Affects: Every public TLS certificate.
Check
# When the certificate a site is serving expires
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -enddate
What to do: By now renewal has to be fully automatic, everywhere certificates live, load balancers and appliances included.
JavaScript actions run on Node 24. The opt-out, ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION, is gone, and self-hosted runners on macOS 13.4 or earlier, or on ARM32, are no longer supported. Applies to github.com and GitHub with Data Residency.
Affects: Workflows using old releases of JavaScript actions, and maintainers of such actions.
Check
# In an action you maintain
grep -n "using:" action.yml
What to do: Update actions to releases that run on node24; if you maintain one, set runs.using to node24 and publish a release.
EU Cyber Resilience Act: vulnerability reporting applies
Manufacturers must report actively exploited vulnerabilities and severe incidents in their products with digital elements, including products already on the EU market.
Affects: Anyone who places software or connected products on the EU market.
What to do: Know who reports, to whom and how fast; the Commission's page links the details.
The community Ingress NGINX controller stopped receiving releases, including security fixes. F5's NGINX Ingress Controller is a different project and is not affected.
Affects: Clusters whose Ingress objects are served by kubernetes/ingress-nginx.
Check (from the Kubernetes blog)
kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx
What to do: Plan the move to Gateway API or another controller, and find the behaviours a literal translation drops before you switch.
Certificates from publicly trusted authorities issued from this date may be valid for at most 200 days, down from 398. The limit falls again in 2027 and 2029.
Affects: Anyone who buys or renews certificates by hand once a year.
Check
# When the certificate a site is serving expires
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -enddate
What to do: Automate renewal now; a yearly manual renewal is no longer possible, and the interval only gets shorter.
Every date read from the source that sets it on 22 October 2026. Checks run where a system was available; otherwise the source of the command is named beside it.