BEGIN:VCALENDAR VERSION:2.0 PRODID:-//CyberNative AI LLC//Breakage Calendar//EN CALSCALE:GREGORIAN METHOD:PUBLISH X-WR-CALNAME:CyberNative Breakage Calendar X-WR-CALDESC:Dated infrastructure changes that will break running systems: who is affected\, how to check\, and a tested fix where we have one. https ://cybernative.ai/breakage-calendar/ REFRESH-INTERVAL;VALUE=DURATION:P1D X-PUBLISHED-TTL:P1D SOURCE;VALUE=URI:https://cybernative.ai/breakage-calendar/breakage-calendar .ics BEGIN:VEVENT UID:2026-10-01-tls-200-day-certificates-first-expiries@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261001 DTEND;VALUE=DATE:20261002 SUMMARY:First 200-day TLS certificates expire DESCRIPTION:Since 15 March 2026\, publicly trusted TLS certificates can be valid for at most 200 days\, down from 398. A certificate issued on 15 Mar ch with the full 200 days expired on 1 October 2026\, so certificates now need renewing at least twice a year.\n\nWhen: 1 October 2026.\n\nWho is af fected: Anyone who renews certificates by hand or plans renewals around a once-a-year reminder. Automated renewal now has to succeed at least twice a year.\n\nHow to check: Read your live certificate's dates (replace examp le.com with your host). If the gap between notBefore and notAfter is 200 d ays or less\, it will not last a year.\necho | openssl s_client -connect e xample.com:443 \\\n 2>/dev/null | openssl x509 -noout -startdate -enddate \n\nFix: No tested fix yet. CA/Browser Forum Baseline Requirements (dates in section 1.2.2): https://cabforum.org/working-groups/server/baseline-req uirements/requirements/\n\nSource: CA/Browser Forum TLS Baseline Requireme nts: maximum validity 200 days from 2026-03-15 https://cabforum.org/workin g-groups/server/baseline-requirements/requirements/\n\nFrom the CyberNativ e Breakage Calendar: https://cybernative.ai/breakage-calendar/#2026-10-01- tls-200-day-certificates-first-expiries URL:https://cybernative.ai/breakage-calendar/#2026-10-01-tls-200-day-certif icates-first-expiries CATEGORIES:Certificates TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-10-09-python-3-15-pip-installs-old-releases@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261009 DTEND;VALUE=DATE:20261010 SUMMARY:Python 3.15: pip may install years-old releases DESCRIPTION:Python 3.15.0 was released on 9 October 2026. Some popular pack ages declare a requires_python that stops below 3.15\; on 3.15\, pip skips those releases and installs an older one without a warning\, while uv ign ores the cap and installs the latest.\n\nWhen: 9 October 2026.\n\nWho is a ffected: Projects moving to Python 3.15 that depend on packages with a req uires_python cap below 3.15. In our wheels-only test with pip 26.2.1 on 11 October\, that included aiogram\, great-expectations\, youtube-transcript -api\, voyageai and modal (old releases installed)\, and dagster\, prefect \, google-ads\, mistral-common and snowflake (install fails without naming the cap).\n\nHow to check: Resolve your requirements with the Python you use today\, then run our cap315.py on the report: it lists every resolved release that excludes 3.15 and exits 1 if any does. The two commands are i n the guide. To also run your own tests on 3.15 beside your newest Python every week\, add our free Future CI workflow: https://github.com/CyberNati ve-AI/future-ci\n\nFix: Guide: Check script and what to do: put a floor on direct dependencies so pip fails loudly. https://github.com/CyberNative-A I/.github/tree/main/notes/python315-install-fallback\n\nSource: Python 3.1 5.0 release page (python.org) https://www.python.org/downloads/release/pyt hon-3150/\n\nFrom the CyberNative Breakage Calendar: https://cybernative.a i/breakage-calendar/#2026-10-09-python-3-15-pip-installs-old-releases URL:https://cybernative.ai/breakage-calendar/#2026-10-09-python-3-15-pip-in stalls-old-releases CATEGORIES:Python TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-10-11-root-ksk-2024-dnssec-rollover@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261011 DTEND;VALUE=DATE:20261012 SUMMARY:DNS root key roll: old trust anchors fail DESCRIPTION:On 11 October 2026 the DNS root zone began using only its new k ey-signing key\, KSK-2024 (key tag 38696). A DNSSEC-validating resolver th at does not trust it fails to resolve names.\n\nWhen: 11 October 2026.\n\n Who is affected: Validating resolvers whose built-in or configured trust a nchor has only the 2017 key\, for example systemd-resolved on Ubuntu 22.04 and 24.04\, fresh BIND installs on Ubuntu 20.04 and Debian 11\, and some routers\, Pi-hole setups and DNS server images.\n\nHow to check: Ask your own validating resolver for a signed name. SERVFAIL\, or "BOGUS DNSKEY" in its log\, is the symptom\; the guide has a check for each resolver that s hows whether it trusts the new key.\nresolvectl query example.com\ndig @12 7.0.0.1 example.com\n\nFix: Tested fix: Tested fixes for systemd-resolved\ , BIND\, Unbound\, PowerDNS\, dnsmasq and Pi-hole. https://cybernative.ai/ guides/root-ksk-2024-dnssec-fixes/\n\nSource: ICANN: Preparing for the roo t zone KSK rollover https://www.icann.org/en/blogs/details/preparing-for-t he-root-zone-ksk-rollover-what-you-need-to-know-27-07-2026-en\n\nFrom the CyberNative Breakage Calendar: https://cybernative.ai/breakage-calendar/#2 026-10-11-root-ksk-2024-dnssec-rollover URL:https://cybernative.ai/breakage-calendar/#2026-10-11-root-ksk-2024-dnss ec-rollover CATEGORIES:DNS TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-10-13-python-3-16-asyncio-policy-removal@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261013 DTEND;VALUE=DATE:20261014 SUMMARY:Python 3.16 alpha breaks pytest-asyncio DESCRIPTION:Python 3.16.0a1\, released 13 October 2026\, removes asyncio's event loop policy system and asyncio.iscoroutinefunction()\, both deprecat ed since 3.14.\n\nWhen: 13 October 2026.\n\nWho is affected: Projects that add Python 3.16 to CI. With pytest-asyncio 1.4.0 (the current release) in stalled\, every test errors at setup\, including plain synchronous tests. Code that calls get_event_loop_policy() or set_event_loop_policy() fails t oo.\n\nHow to check: See whether pytest-asyncio is installed and which ver sion. Version 1.4.0 or older errors on 3.16\; deprecation-warnings-as-erro rs on 3.15 does not catch it.\npip show pytest-asyncio\n\nFix: Tested fix: Tested conftest.py stopgap for pytest-asyncio\, plus an iscoroutinefuncti on shim. https://github.com/CyberNative-AI/.github/tree/main/notes/python- 316-asyncio-removals\n\nSource: What's New in Python 3.16\, Removed: async io https://docs.python.org/3.16/whatsnew/3.16.html\; PEP 826: Python 3.16 release schedule https://peps.python.org/pep-0826/\n\nFrom the CyberNative Breakage Calendar: https://cybernative.ai/breakage-calendar/#2026-10-13-p ython-3-16-asyncio-policy-removal URL:https://cybernative.ai/breakage-calendar/#2026-10-13-python-3-16-asynci o-policy-removal CATEGORIES:Python TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-10-16-github-macos-14-brownouts-20261016@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261016 DTEND;VALUE=DATE:20261017 SUMMARY:macOS 14 brownout: jobs fail 14:00–24:00 UTC DESCRIPTION:GitHub makes jobs on the macOS 14 image fail for ten hours on s ix days before it retires the image: 14:00 UTC to midnight UTC on 16\, 19\ , 23\, 26\, 29 and 30 October 2026.\n\nWhen: 16–30 October 2026\, 14:00 to 24:00 UTC on each brownout day.\n\nWho is affected: Workflows that use the labels macos-14\, macos-14-large or macos-14-xlarge.\n\nHow to check: From your repository root\, search the workflow files for the old labels ( needs ripgrep). Read every match\, including matrix entries.\nrg -n --hidd en --glob '*.yml' --glob '*.yaml' \\\n '\\bmacos-14(-large|-xlarge)?\\b' .github/workflows\n\nFix: Guide: Find the labels\, pick the replacement by architecture\, check Xcode and simulators. https://github.com/CyberNative -AI/.github/tree/main/notes/macos14-brownout\n\nSource: GitHub changelog: macOS 14 runner image retirement (1 October 2026) https://github.blog/chan gelog/2026-10-01-github-actions-macos-14-runner-image-retirement/\n\nFrom the CyberNative Breakage Calendar: https://cybernative.ai/breakage-calenda r/#2026-10-16-github-macos-14-brownouts URL:https://cybernative.ai/breakage-calendar/#2026-10-16-github-macos-14-br ownouts CATEGORIES:CI runners TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-10-16-github-macos-14-brownouts-20261019@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261019 DTEND;VALUE=DATE:20261020 SUMMARY:macOS 14 brownout: jobs fail 14:00–24:00 UTC DESCRIPTION:GitHub makes jobs on the macOS 14 image fail for ten hours on s ix days before it retires the image: 14:00 UTC to midnight UTC on 16\, 19\ , 23\, 26\, 29 and 30 October 2026.\n\nWhen: 16–30 October 2026\, 14:00 to 24:00 UTC on each brownout day.\n\nWho is affected: Workflows that use the labels macos-14\, macos-14-large or macos-14-xlarge.\n\nHow to check: From your repository root\, search the workflow files for the old labels ( needs ripgrep). Read every match\, including matrix entries.\nrg -n --hidd en --glob '*.yml' --glob '*.yaml' \\\n '\\bmacos-14(-large|-xlarge)?\\b' .github/workflows\n\nFix: Guide: Find the labels\, pick the replacement by architecture\, check Xcode and simulators. https://github.com/CyberNative -AI/.github/tree/main/notes/macos14-brownout\n\nSource: GitHub changelog: macOS 14 runner image retirement (1 October 2026) https://github.blog/chan gelog/2026-10-01-github-actions-macos-14-runner-image-retirement/\n\nFrom the CyberNative Breakage Calendar: https://cybernative.ai/breakage-calenda r/#2026-10-16-github-macos-14-brownouts URL:https://cybernative.ai/breakage-calendar/#2026-10-16-github-macos-14-br ownouts CATEGORIES:CI runners TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-10-16-github-macos-14-brownouts-20261023@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261023 DTEND;VALUE=DATE:20261024 SUMMARY:macOS 14 brownout: jobs fail 14:00–24:00 UTC DESCRIPTION:GitHub makes jobs on the macOS 14 image fail for ten hours on s ix days before it retires the image: 14:00 UTC to midnight UTC on 16\, 19\ , 23\, 26\, 29 and 30 October 2026.\n\nWhen: 16–30 October 2026\, 14:00 to 24:00 UTC on each brownout day.\n\nWho is affected: Workflows that use the labels macos-14\, macos-14-large or macos-14-xlarge.\n\nHow to check: From your repository root\, search the workflow files for the old labels ( needs ripgrep). Read every match\, including matrix entries.\nrg -n --hidd en --glob '*.yml' --glob '*.yaml' \\\n '\\bmacos-14(-large|-xlarge)?\\b' .github/workflows\n\nFix: Guide: Find the labels\, pick the replacement by architecture\, check Xcode and simulators. https://github.com/CyberNative -AI/.github/tree/main/notes/macos14-brownout\n\nSource: GitHub changelog: macOS 14 runner image retirement (1 October 2026) https://github.blog/chan gelog/2026-10-01-github-actions-macos-14-runner-image-retirement/\n\nFrom the CyberNative Breakage Calendar: https://cybernative.ai/breakage-calenda r/#2026-10-16-github-macos-14-brownouts URL:https://cybernative.ai/breakage-calendar/#2026-10-16-github-macos-14-br ownouts CATEGORIES:CI runners TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-10-16-github-macos-14-brownouts-20261026@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261026 DTEND;VALUE=DATE:20261027 SUMMARY:macOS 14 brownout: jobs fail 14:00–24:00 UTC DESCRIPTION:GitHub makes jobs on the macOS 14 image fail for ten hours on s ix days before it retires the image: 14:00 UTC to midnight UTC on 16\, 19\ , 23\, 26\, 29 and 30 October 2026.\n\nWhen: 16–30 October 2026\, 14:00 to 24:00 UTC on each brownout day.\n\nWho is affected: Workflows that use the labels macos-14\, macos-14-large or macos-14-xlarge.\n\nHow to check: From your repository root\, search the workflow files for the old labels ( needs ripgrep). Read every match\, including matrix entries.\nrg -n --hidd en --glob '*.yml' --glob '*.yaml' \\\n '\\bmacos-14(-large|-xlarge)?\\b' .github/workflows\n\nFix: Guide: Find the labels\, pick the replacement by architecture\, check Xcode and simulators. https://github.com/CyberNative -AI/.github/tree/main/notes/macos14-brownout\n\nSource: GitHub changelog: macOS 14 runner image retirement (1 October 2026) https://github.blog/chan gelog/2026-10-01-github-actions-macos-14-runner-image-retirement/\n\nFrom the CyberNative Breakage Calendar: https://cybernative.ai/breakage-calenda r/#2026-10-16-github-macos-14-brownouts URL:https://cybernative.ai/breakage-calendar/#2026-10-16-github-macos-14-br ownouts CATEGORIES:CI runners TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-10-16-github-macos-14-brownouts-20261029@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261029 DTEND;VALUE=DATE:20261030 SUMMARY:macOS 14 brownout: jobs fail 14:00–24:00 UTC DESCRIPTION:GitHub makes jobs on the macOS 14 image fail for ten hours on s ix days before it retires the image: 14:00 UTC to midnight UTC on 16\, 19\ , 23\, 26\, 29 and 30 October 2026.\n\nWhen: 16–30 October 2026\, 14:00 to 24:00 UTC on each brownout day.\n\nWho is affected: Workflows that use the labels macos-14\, macos-14-large or macos-14-xlarge.\n\nHow to check: From your repository root\, search the workflow files for the old labels ( needs ripgrep). Read every match\, including matrix entries.\nrg -n --hidd en --glob '*.yml' --glob '*.yaml' \\\n '\\bmacos-14(-large|-xlarge)?\\b' .github/workflows\n\nFix: Guide: Find the labels\, pick the replacement by architecture\, check Xcode and simulators. https://github.com/CyberNative -AI/.github/tree/main/notes/macos14-brownout\n\nSource: GitHub changelog: macOS 14 runner image retirement (1 October 2026) https://github.blog/chan gelog/2026-10-01-github-actions-macos-14-runner-image-retirement/\n\nFrom the CyberNative Breakage Calendar: https://cybernative.ai/breakage-calenda r/#2026-10-16-github-macos-14-brownouts URL:https://cybernative.ai/breakage-calendar/#2026-10-16-github-macos-14-br ownouts CATEGORIES:CI runners TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-10-16-github-macos-14-brownouts-20261030@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261030 DTEND;VALUE=DATE:20261031 SUMMARY:macOS 14 brownout: jobs fail 14:00–24:00 UTC DESCRIPTION:GitHub makes jobs on the macOS 14 image fail for ten hours on s ix days before it retires the image: 14:00 UTC to midnight UTC on 16\, 19\ , 23\, 26\, 29 and 30 October 2026.\n\nWhen: 16–30 October 2026\, 14:00 to 24:00 UTC on each brownout day.\n\nWho is affected: Workflows that use the labels macos-14\, macos-14-large or macos-14-xlarge.\n\nHow to check: From your repository root\, search the workflow files for the old labels ( needs ripgrep). Read every match\, including matrix entries.\nrg -n --hidd en --glob '*.yml' --glob '*.yaml' \\\n '\\bmacos-14(-large|-xlarge)?\\b' .github/workflows\n\nFix: Guide: Find the labels\, pick the replacement by architecture\, check Xcode and simulators. https://github.com/CyberNative -AI/.github/tree/main/notes/macos14-brownout\n\nSource: GitHub changelog: macOS 14 runner image retirement (1 October 2026) https://github.blog/chan gelog/2026-10-01-github-actions-macos-14-runner-image-retirement/\n\nFrom the CyberNative Breakage Calendar: https://cybernative.ai/breakage-calenda r/#2026-10-16-github-macos-14-brownouts URL:https://cybernative.ai/breakage-calendar/#2026-10-16-github-macos-14-br ownouts CATEGORIES:CI runners TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-10-19-ubuntu-latest-26-04-erlang-setup-beam@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261019 DTEND;VALUE=DATE:20261120 SUMMARY:ubuntu-latest → 26.04: Erlang OTP 24/25 fail DESCRIPTION:As ubuntu-latest moves to Ubuntu 26.04 (19 October to 19 Novemb er 2026)\, erlef/setup-beam installs Erlang/OTP builds made for 26.04\, an d that build list starts at OTP 26.0.\n\nWhen: 19 October 2026 to 19 Novem ber 2026.\n\nWho is affected: Elixir and Erlang jobs on ubuntu-latest that ask for OTP 24 or 25\, and any job pinned to setup-beam v1.24.0 or earlie r\, which does not recognise the 26.04 image whatever OTP version it asks for. Of 224 popular Hex packages' repositories that run setup-beam on ubun tu-latest\, 89 had a job that fails this way.\n\nHow to check: Run our che ckbeam2604.py on your repository\; it needs no token and runs nothing from the repository. The download and run commands are in the note.\n\nFix: Gu ide: Checker and fixes per entry: keep old OTP on ubuntu-24.04\, raise to OTP 26+\, or update setup-beam. https://github.com/CyberNative-AI/.github/ tree/main/notes/ubuntu-2604-setup-beam\n\nSource: actions/runner-images is sue #14748: ubuntu-latest becomes Ubuntu 26.04 https://github.com/actions/ runner-images/issues/14748\n\nFrom the CyberNative Breakage Calendar: http s://cybernative.ai/breakage-calendar/#2026-10-19-ubuntu-latest-26-04-erlan g-setup-beam URL:https://cybernative.ai/breakage-calendar/#2026-10-19-ubuntu-latest-26-0 4-erlang-setup-beam CATEGORIES:CI runners TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-10-19-ubuntu-latest-26-04-python-ruby-setup@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261019 DTEND;VALUE=DATE:20261120 SUMMARY:ubuntu-latest → 26.04: Python/Ruby setup fails DESCRIPTION:GitHub rolls the ubuntu-latest label from Ubuntu 24.04 to 26.04 over several weeks\, starting 19 October and finishing by 19 November 202 6. actions/setup-python and ruby/setup-ruby download a build made for the exact Ubuntu version\, and far fewer builds exist for 26.04.\n\nWhen: 19 O ctober 2026 to 19 November 2026.\n\nWho is affected: Jobs on ubuntu-latest that ask for a Python or Ruby version with no 26.04 build: an old version such as Python 3.8 or 3.9\, or an exact patch version\, including pins in .python-version or .ruby-version. In a sample of 548 active public reposi tories\, 122 had at least one such job.\n\nHow to check: Open our browser check and choose your repository folder. It reads only the workflow and ve rsion files and lists every step that fails at setup on 26.04\, with its f ix. To run your own tests on ubuntu-26.04 beside a 24.04 baseline every we ek\, add our free Future CI workflow: https://github.com/CyberNative-AI/fu ture-ci\n\nFix: Tested fix: Browser check and fixes per entry\; tested rou te for Python 3.8 and 3.9 on 26.04 (none yet for Ruby before 3.2). https:/ /cybernative.ai/tools/ubuntu-2604-check/\n\nSource: actions/runner-images issue #14748: ubuntu-latest becomes Ubuntu 26.04 https://github.com/action s/runner-images/issues/14748\n\nFrom the CyberNative Breakage Calendar: ht tps://cybernative.ai/breakage-calendar/#2026-10-19-ubuntu-latest-26-04-pyt hon-ruby-setup URL:https://cybernative.ai/breakage-calendar/#2026-10-19-ubuntu-latest-26-0 4-python-ruby-setup CATEGORIES:CI runners TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-10-25-europe-clocks-go-back-schedulers@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261025 DTEND;VALUE=DATE:20261026 SUMMARY:UK/EU clocks go back: some jobs run twice DESCRIPTION:The UK and the EU end summer time on 25 October 2026\, so one l ocal hour happens twice: 01:00 to 01:59 in London\, 02:00 to 02:59 in Berl in.\n\nWhen: 25 October 2026\, 01:00 UTC.\n\nWho is affected: In our contr olled-clock tests for London\, cron 4.4.0 and node-schedule 2.1.1 ran half -hourly jobs twice in the repeated hour\, and a daily cron job set just af ter it also fired once early. An n8n 2.40.7 daily 03:00 Schedule Trigger i n Europe/Berlin fired twice\, the extra run one hour early. Other versions and schedulers were not tested.\n\nHow to check: Run our dst-check agains t your own expression\, time zone and installed scheduler version before t he change. It labels each callback ok\, MISSED\, DUPLICATED or SHIFTED.\n\ nFix: Guide: Measured results per library and a check for your schedule (n o tested fix). https://github.com/CyberNative-AI/.github/tree/main/notes/j avascript-dst-2026\n\nSource: GOV.UK: When do the clocks change? https://w ww.gov.uk/when-do-the-clocks-change\; PTB (Germany's national time authori ty): when summer time begins and ends https://www.ptb.de/cms/ptb/fachabtei lungen/abt4/fb-44/fragenzurzeit/fragenzurzeit03.html\n\nFrom the CyberNati ve Breakage Calendar: https://cybernative.ai/breakage-calendar/#2026-10-25 -europe-clocks-go-back-schedulers URL:https://cybernative.ai/breakage-calendar/#2026-10-25-europe-clocks-go-b ack-schedulers CATEGORIES:Time zones TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-11-01-canada-time-zone-change-databases@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261101 DTEND;VALUE=DATE:20261102 SUMMARY:Canada time change: databases an hour off DESCRIPTION:Alberta\, the Northwest Territories\, Manitoba and British Colu mbia stop falling back on 1 November 2026. These data platforms carry thei r own copy of the time-zone rules\, separate from the operating system's.\ n\nWhen: 1 November 2026\, 02:00 local.\n\nWho is affected: Self-managed M ongoDB\, Elasticsearch\, OpenSearch\, Trino and DuckDB that report or buck et times in Canadian local time\, or in Moroccan time\, which old rules ha ve had wrong since 20 September. Their newest releases were still wrong on 14 October.\n\nHow to check: Each engine has a one-line query in the guid e that converts 15 December 2026 12:00 UTC to America/Winnipeg. The right answer is 07:00 (UTC-05)\; 06:00 means stale rules.\n\nFix: Tested fix: Te sted fixes for MongoDB\, Elasticsearch/OpenSearch\, Trino and DuckDB. http s://cybernative.ai/guides/canada-time-zone-change-2026-databases/\n\nSourc e: IANA time zone database 2026e release notes https://data.iana.org/time- zones/tzdb/NEWS\n\nFrom the CyberNative Breakage Calendar: https://cyberna tive.ai/breakage-calendar/#2026-11-01-canada-time-zone-change-databases URL:https://cybernative.ai/breakage-calendar/#2026-11-01-canada-time-zone-c hange-databases CATEGORIES:Time zones TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-11-01-canada-time-zone-change-runtimes@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261101 DTEND;VALUE=DATE:20261102 SUMMARY:Canada time change: Java\, Go\, PHP an hour off DESCRIPTION:On 1 November 2026 Alberta\, the Northwest Territories\, Manito ba and British Columbia stop falling back. Rules older than IANA release 2 026e show Calgary\, Edmonton\, Inuvik and Winnipeg an hour behind\; rules older than April 2026 also get Vancouver wrong. Ontario has announced\, bu t not yet published\, the same for northwestern Ontario west of the 90th m eridian\, including Kenora\; 2026e already includes it\, so the same fixes cover it.\n\nWhen: 1 November 2026\, 02:00 local.\n\nWho is affected: Sof tware that carries its own copy of the time-zone rules: every current Ecli pse Temurin LTS Java (2026b\; Temurin's October update is due 20 October)\ , Go's built-in copy\, PHP 8.2 and 8.3\, Rust chrono-tz\, Kubernetes CronJ obs with timeZone (controller images on 2026b)\, and MySQL and MariaDB nam ed time zones loaded before the change. Debian and Ubuntu packages were st ill on 2026c on 13 October.\n\nHow to check: These print the PHP and Node. js rules versions and the system's December time in Winnipeg. You want 202 6e (PHP: 2026.5) and 07:00\; anything older is an hour off for at least on e zone. For Java\, Go and the rest\, see the guide.\nphp -r 'echo timezone _version_get()\, "\\n"\;'\nnode -p process.versions.tz\nTZ=America/Winnipe g date -d '2026-12-15 12:00Z' +%H:%M\n\nFix: Tested fix: Tested fixes for Java\, PHP\, Go\, Kubernetes CronJobs and MySQL/MariaDB. https://cybernati ve.ai/guides/canada-time-zone-change-2026-runtimes/\n\nSource: IANA time z one database 2026e release notes https://data.iana.org/time-zones/tzdb/NEW S\; Government of Ontario: permanent daylight saving time in parts of nort hwestern Ontario (13 October 2026) https://news.ontario.ca/en/release/1008 130/ontario_moving_to_permanent_daylight_saving_time_in_parts_of_northwest ern_ontario\n\nFrom the CyberNative Breakage Calendar: https://cybernative .ai/breakage-calendar/#2026-11-01-canada-time-zone-change-runtimes URL:https://cybernative.ai/breakage-calendar/#2026-11-01-canada-time-zone-c hange-runtimes CATEGORIES:Time zones TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-11-01-us-clocks-go-back-schedulers@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261101 DTEND;VALUE=DATE:20261102 SUMMARY:US clocks go back: some jobs run twice DESCRIPTION:Daylight saving time ends in most of the US at 02:00 local time on 1 November 2026\, so 01:00 to 01:59 happens twice.\n\nWhen: 1 November 2026\, 02:00 local.\n\nWho is affected: In our controlled-clock tests\, c ron 4.4.0 and node-schedule 2.1.1 ran half-hourly jobs twice in the repeat ed hour\, node-cron 4.6.0 picked different occurrences in New York and Lon don\, and an n8n 2.40.7 daily 02:30 Schedule Trigger in America/New_York f ired twice\, the extra run at 01:30. Other versions and schedulers were no t tested.\n\nHow to check: Run our dst-check against your own expression\, time zone and installed scheduler version before the change. It labels ea ch callback ok\, MISSED\, DUPLICATED or SHIFTED.\n\nFix: Guide: Measured r esults per library and a check for your schedule (no tested fix). https:// github.com/CyberNative-AI/.github/tree/main/notes/javascript-dst-2026\n\nS ource: NIST: Daylight saving time rules https://www.nist.gov/pml/time-and- frequency-division/popular-links/daylight-saving-time-dst\n\nFrom the Cybe rNative Breakage Calendar: https://cybernative.ai/breakage-calendar/#2026- 11-01-us-clocks-go-back-schedulers URL:https://cybernative.ai/breakage-calendar/#2026-11-01-us-clocks-go-back- schedulers CATEGORIES:Time zones TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-11-02-github-macos-14-runner-retirement@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261102 DTEND;VALUE=DATE:20261103 SUMMARY:GitHub retires the macOS 14 runner DESCRIPTION:GitHub retires the macOS 14 runner image on 2 November 2026. Xc ode 15\, the iOS 17\, 18.1 and 18.2 simulator runtimes and the iPhone 15 s imulator devices are installed only on the macOS 14 images.\n\nWhen: 2 Nov ember 2026.\n\nWho is affected: Workflows that use macos-14\, macos-14-lar ge or macos-14-xlarge\, and jobs that select Xcode 15\, an iOS 17\, 18.1 o r 18.2 simulator or an iPhone 15 simulator\, which no remaining image has. \n\nHow to check: From your repository root\, search the workflow files fo r the old labels (needs ripgrep)\, then check each matching job's Xcode an d simulator selections.\nrg -n --hidden --glob '*.yml' --glob '*.yaml' \\\ n '\\bmacos-14(-large|-xlarge)?\\b' .github/workflows\n\nFix: Guide: Repl acement by architecture\, and which Xcode and simulators each image has. h ttps://github.com/CyberNative-AI/.github/tree/main/notes/macos14-brownout# check-xcode-and-simulator-selections-too\n\nSource: GitHub changelog: macO S 14 runner image retirement (1 October 2026) https://github.blog/changelo g/2026-10-01-github-actions-macos-14-runner-image-retirement/\n\nFrom the CyberNative Breakage Calendar: https://cybernative.ai/breakage-calendar/#2 026-11-02-github-macos-14-runner-retirement URL:https://cybernative.ai/breakage-calendar/#2026-11-02-github-macos-14-ru nner-retirement CATEGORIES:CI runners TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-11-16-usgs-waterservices-slowdown@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261116 DTEND;VALUE=DATE:20261117 SUMMARY:USGS WaterServices: 2 s delay per request DESCRIPTION:From 16 November 2026\, USGS adds a 2-second delay to every req uest to waterservices.usgs.gov. The delay rises to 10 seconds on 11 Januar y\, 30 seconds on 25 January and 60 seconds on 1 February 2027. Requests a re also redirected instead of answered for about 24 hours on 27 January an d about 48 hours on 15 February.\n\nWhen: 16 November 2026.\n\nWho is affe cted: Scripts\, dashboards and pipelines that call waterservices.usgs.gov\ , especially those making many requests or running under a timeout.\n\nHow to check: Search your code and configuration for the old host.\ngrep -rn 'waterservices.usgs.gov' .\n\nFix: No tested fix yet. USGS migration guide to the new Water Data APIs: https://api.waterdata.usgs.gov/docs/ogcapi/mi gration/\n\nSource: USGS: WaterServices degradation and decommission sched ule (18 September 2026) https://waterdata.usgs.gov/blog/wdfn-waterservices -degradation/\n\nFrom the CyberNative Breakage Calendar: https://cybernati ve.ai/breakage-calendar/#2026-11-16-usgs-waterservices-slowdown URL:https://cybernative.ai/breakage-calendar/#2026-11-16-usgs-waterservices -slowdown CATEGORIES:Data APIs TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2026-12-16-socrata-soda1-removal@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261216 DTEND;VALUE=DATE:20261217 SUMMARY:Socrata removes SODA1 rows.csv downloads DESCRIPTION:Tyler Technologies removes Socrata's SODA1 API on 16 December 2 026. Links of the form /api/views/{dataset-id}/rows.csv?accessType=DOWNLOA D stop working\; the documented replacement\, export.csv\, keeps column na mes but can turn numbers into formatted text.\n\nWhen: 16 December 2026.\n \nWho is affected: Scripts\, notebooks and dashboards that download open-d ata portals' rows.csv files. In 65 of 120 popular datasets we sampled\, ex port.csv turned at least one plain-number column into formatted text.\n\nH ow to check: Search your code for SODA1 download links\, then paste each o ne into the checker on the guide page.\ngrep -rn 'accessType=DOWNLOAD' .\n \nFix: Tested fix: Replacement URL plus pandas and R code that keeps the o ld column names and numbers. https://cybernative.ai/guides/socrata-rows-cs v-replacement/\n\nSource: Tyler Technologies (Socrata): Deprecation Roadma p https://support.socrata.com/hc/en-us/articles/360008097514-Deprecation-R oadmap\n\nFrom the CyberNative Breakage Calendar: https://cybernative.ai/b reakage-calendar/#2026-12-16-socrata-soda1-removal URL:https://cybernative.ai/breakage-calendar/#2026-12-16-socrata-soda1-remo val CATEGORIES:Data APIs TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2027-02-22-usgs-waterservices-decommissioned@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20270222 DTEND;VALUE=DATE:20270223 SUMMARY:USGS WaterServices shut down DESCRIPTION:USGS decommissions WaterServices on 22 February 2027. From that day\, every request to waterservices.usgs.gov is redirected to a decommis sioning blog post instead of returning data.\n\nWhen: 22 February 2027.\n\ nWho is affected: Anything still calling waterservices.usgs.gov instead of the new Water Data APIs.\n\nHow to check: Search your code and configurat ion for the old host.\ngrep -rn 'waterservices.usgs.gov' .\n\nFix: No test ed fix yet. USGS migration guide to the new Water Data APIs: https://api.w aterdata.usgs.gov/docs/ogcapi/migration/\n\nSource: USGS: WaterServices de gradation and decommission schedule (18 September 2026) https://waterdata. usgs.gov/blog/wdfn-waterservices-degradation/\n\nFrom the CyberNative Brea kage Calendar: https://cybernative.ai/breakage-calendar/#2027-02-22-usgs-w aterservices-decommissioned URL:https://cybernative.ai/breakage-calendar/#2027-02-22-usgs-waterservices -decommissioned CATEGORIES:Data APIs TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:2027-03-15-tls-100-day-certificates@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20270315 DTEND;VALUE=DATE:20270316 SUMMARY:TLS certificate maximum drops to 100 days DESCRIPTION:From 15 March 2027\, publicly trusted TLS certificates can be v alid for at most 100 days\, and domain validation can be reused for at mos t 100 days\, down from 200 for both.\n\nWhen: 15 March 2027.\n\nWho is aff ected: Anyone who renews certificates by hand or on a fixed schedule built around 200-day certificates. Renewal will be needed at least every 100 da ys\, about four times a year.\n\nHow to check: Read your live certificate' s dates (replace example.com with your host) to see how long your current certificates last.\necho | openssl s_client -connect example.com:443 \\\n 2>/dev/null | openssl x509 -noout -startdate -enddate\n\nFix: No tested f ix yet. CA/Browser Forum Baseline Requirements (dates in section 1.2.2): h ttps://cabforum.org/working-groups/server/baseline-requirements/requiremen ts/\n\nSource: CA/Browser Forum TLS Baseline Requirements: maximum validit y 100 days from 2027-03-15 https://cabforum.org/working-groups/server/base line-requirements/requirements/\n\nFrom the CyberNative Breakage Calendar: https://cybernative.ai/breakage-calendar/#2027-03-15-tls-100-day-certific ates URL:https://cybernative.ai/breakage-calendar/#2027-03-15-tls-100-day-certif icates CATEGORIES:Certificates TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20261012@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261012 DTEND;VALUE=DATE:20261019 SUMMARY:Check this week: 8 changes\, soonest Oct 19 DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nOct 19\, 23\, 26\, 29 and 30 · Guide · newly listed\nmacOS 14 brownout: jobs fail 14:00–24:00 UTC\nhttps://cybernative.ai/breakage-calendar/#20 26-10-16-github-macos-14-brownouts\n\nFrom Oct 19 · Guide · newly listed \nubuntu-latest → 26.04: Erlang OTP 24/25 fail\nhttps://cybernative.ai/b reakage-calendar/#2026-10-19-ubuntu-latest-26-04-erlang-setup-beam\n\nFrom Oct 19 · Tested fix · newly listed\nubuntu-latest → 26.04: Python/Rub y setup fails\nhttps://cybernative.ai/breakage-calendar/#2026-10-19-ubuntu -latest-26-04-python-ruby-setup\n\nOct 25 · Guide · newly listed\nUK/EU clocks go back: some jobs run twice\nhttps://cybernative.ai/breakage-calen dar/#2026-10-25-europe-clocks-go-back-schedulers\n\nNov 1 · Tested fix · newly listed\nCanada time change: databases an hour off\nhttps://cybernat ive.ai/breakage-calendar/#2026-11-01-canada-time-zone-change-databases\n\n Nov 1 · Tested fix · newly listed\nCanada time change: Java\, Go\, PHP a n hour off\nhttps://cybernative.ai/breakage-calendar/#2026-11-01-canada-ti me-zone-change-runtimes\n\nNov 1 · Guide · newly listed\nUS clocks go ba ck: some jobs run twice\nhttps://cybernative.ai/breakage-calendar/#2026-11 -01-us-clocks-go-back-schedulers\n\nNov 16 · No tested fix yet · newly l isted\nUSGS WaterServices: 2 s delay per request\nhttps://cybernative.ai/b reakage-calendar/#2026-11-16-usgs-waterservices-slowdown\n\nThe whole cale ndar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT BEGIN:VALARM ACTION:DISPLAY TRIGGER:PT9H DESCRIPTION:Check this week: 8 changes\, soonest Oct 19 END:VALARM END:VEVENT BEGIN:VEVENT UID:week-20261019@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261019 DTEND;VALUE=DATE:20261026 SUMMARY:Check this week: 9 changes\, soonest Oct 19 DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nOct 19\, 23\, 26\, 29 and 30 · Guide\nmacOS 14 brownout: jobs fail 14:00 –24:00 UTC\nhttps://cybernative.ai/breakage-calendar/#2026-10-16-github- macos-14-brownouts\n\nFrom Oct 19 · Guide\nubuntu-latest → 26.04: Erlan g OTP 24/25 fail\nhttps://cybernative.ai/breakage-calendar/#2026-10-19-ubu ntu-latest-26-04-erlang-setup-beam\n\nFrom Oct 19 · Tested fix\nubuntu-la test → 26.04: Python/Ruby setup fails\nhttps://cybernative.ai/breakage-c alendar/#2026-10-19-ubuntu-latest-26-04-python-ruby-setup\n\nOct 25 · Gui de\nUK/EU clocks go back: some jobs run twice\nhttps://cybernative.ai/brea kage-calendar/#2026-10-25-europe-clocks-go-back-schedulers\n\nNov 1 · Tes ted fix\nCanada time change: databases an hour off\nhttps://cybernative.ai /breakage-calendar/#2026-11-01-canada-time-zone-change-databases\n\nNov 1 · Tested fix\nCanada time change: Java\, Go\, PHP an hour off\nhttps://cy bernative.ai/breakage-calendar/#2026-11-01-canada-time-zone-change-runtime s\n\nNov 1 · Guide\nUS clocks go back: some jobs run twice\nhttps://cyber native.ai/breakage-calendar/#2026-11-01-us-clocks-go-back-schedulers\n\nNo v 2 · Guide · newly listed\nGitHub retires the macOS 14 runner\nhttps:// cybernative.ai/breakage-calendar/#2026-11-02-github-macos-14-runner-retire ment\n\nNov 16 · No tested fix yet\nUSGS WaterServices: 2 s delay per req uest\nhttps://cybernative.ai/breakage-calendar/#2026-11-16-usgs-waterservi ces-slowdown\n\nThe whole calendar: https://cybernative.ai/breakage-calend ar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT BEGIN:VALARM ACTION:DISPLAY TRIGGER:PT9H DESCRIPTION:Check this week: 9 changes\, soonest Oct 19 END:VALARM END:VEVENT BEGIN:VEVENT UID:week-20261026@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261026 DTEND;VALUE=DATE:20261102 SUMMARY:Check this week: 6 changes\, soonest Oct 26 DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nOct 26\, 29 and 30 · Guide\nmacOS 14 brownout: jobs fail 14:00–24:00 U TC\nhttps://cybernative.ai/breakage-calendar/#2026-10-16-github-macos-14-b rownouts\n\nNov 1 · Tested fix\nCanada time change: databases an hour off \nhttps://cybernative.ai/breakage-calendar/#2026-11-01-canada-time-zone-ch ange-databases\n\nNov 1 · Tested fix\nCanada time change: Java\, Go\, PHP an hour off\nhttps://cybernative.ai/breakage-calendar/#2026-11-01-canada- time-zone-change-runtimes\n\nNov 1 · Guide\nUS clocks go back: some jobs run twice\nhttps://cybernative.ai/breakage-calendar/#2026-11-01-us-clocks- go-back-schedulers\n\nNov 2 · Guide\nGitHub retires the macOS 14 runner\n https://cybernative.ai/breakage-calendar/#2026-11-02-github-macos-14-runne r-retirement\n\nNov 16 · No tested fix yet\nUSGS WaterServices: 2 s delay per request\nhttps://cybernative.ai/breakage-calendar/#2026-11-16-usgs-wa terservices-slowdown\n\nThe whole calendar: https://cybernative.ai/breakag e-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20261102@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261102 DTEND;VALUE=DATE:20261109 SUMMARY:Check this week: 2 changes\, soonest Nov 2 DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nNov 2 · Guide\nGitHub retires the macOS 14 runner\nhttps://cybernative.a i/breakage-calendar/#2026-11-02-github-macos-14-runner-retirement\n\nNov 1 6 · No tested fix yet\nUSGS WaterServices: 2 s delay per request\nhttps:/ /cybernative.ai/breakage-calendar/#2026-11-16-usgs-waterservices-slowdown\ n\nThe whole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20261109@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261109 DTEND;VALUE=DATE:20261116 SUMMARY:Check this week: USGS WaterServices: 2 s delay per request (Nov 16) DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nNov 16 · No tested fix yet\nUSGS WaterServices: 2 s delay per request\nh ttps://cybernative.ai/breakage-calendar/#2026-11-16-usgs-waterservices-slo wdown\n\nThe whole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20261116@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261116 DTEND;VALUE=DATE:20261123 SUMMARY:Check this week: 2 changes\, soonest Nov 16 DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nNov 16 · No tested fix yet\nUSGS WaterServices: 2 s delay per request\nh ttps://cybernative.ai/breakage-calendar/#2026-11-16-usgs-waterservices-slo wdown\n\nDec 16 · Tested fix · newly listed\nSocrata removes SODA1 rows. csv downloads\nhttps://cybernative.ai/breakage-calendar/#2026-12-16-socrat a-soda1-removal\n\nThe whole calendar: https://cybernative.ai/breakage-cal endar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT BEGIN:VALARM ACTION:DISPLAY TRIGGER:PT9H DESCRIPTION:Check this week: 2 changes\, soonest Nov 16 END:VALARM END:VEVENT BEGIN:VEVENT UID:week-20261123@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261123 DTEND;VALUE=DATE:20261130 SUMMARY:Check this week: Socrata removes SODA1 rows.csv downloads (Dec 16) DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nDec 16 · Tested fix\nSocrata removes SODA1 rows.csv downloads\nhttps://c ybernative.ai/breakage-calendar/#2026-12-16-socrata-soda1-removal\n\nThe w hole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20261130@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261130 DTEND;VALUE=DATE:20261207 SUMMARY:Check this week: Socrata removes SODA1 rows.csv downloads (Dec 16) DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nDec 16 · Tested fix\nSocrata removes SODA1 rows.csv downloads\nhttps://c ybernative.ai/breakage-calendar/#2026-12-16-socrata-soda1-removal\n\nThe w hole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20261207@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261207 DTEND;VALUE=DATE:20261214 SUMMARY:Check this week: Socrata removes SODA1 rows.csv downloads (Dec 16) DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nDec 16 · Tested fix\nSocrata removes SODA1 rows.csv downloads\nhttps://c ybernative.ai/breakage-calendar/#2026-12-16-socrata-soda1-removal\n\nThe w hole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20261214@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20261214 DTEND;VALUE=DATE:20261221 SUMMARY:Check this week: Socrata removes SODA1 rows.csv downloads (Dec 16) DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nDec 16 · Tested fix\nSocrata removes SODA1 rows.csv downloads\nhttps://c ybernative.ai/breakage-calendar/#2026-12-16-socrata-soda1-removal\n\nThe w hole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20270111@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20270111 DTEND;VALUE=DATE:20270118 SUMMARY:Check this week: TLS certificate maximum drops to 100 days (Mar 15) DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nMar 15 · No tested fix yet · newly listed\nTLS certificate maximum drop s to 100 days\nhttps://cybernative.ai/breakage-calendar/#2027-03-15-tls-10 0-day-certificates\n\nThe whole calendar: https://cybernative.ai/breakage- calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT BEGIN:VALARM ACTION:DISPLAY TRIGGER:PT9H DESCRIPTION:Check this week: TLS certificate maximum drops to 100 days (Mar 15) END:VALARM END:VEVENT BEGIN:VEVENT UID:week-20270118@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20270118 DTEND;VALUE=DATE:20270125 SUMMARY:Check this week: 2 changes\, soonest Feb 22 DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nFeb 22 · No tested fix yet · newly listed\nUSGS WaterServices shut down \nhttps://cybernative.ai/breakage-calendar/#2027-02-22-usgs-waterservices- decommissioned\n\nMar 15 · No tested fix yet\nTLS certificate maximum dro ps to 100 days\nhttps://cybernative.ai/breakage-calendar/#2027-03-15-tls-1 00-day-certificates\n\nThe whole calendar: https://cybernative.ai/breakage -calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT BEGIN:VALARM ACTION:DISPLAY TRIGGER:PT9H DESCRIPTION:Check this week: 2 changes\, soonest Feb 22 END:VALARM END:VEVENT BEGIN:VEVENT UID:week-20270125@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20270125 DTEND;VALUE=DATE:20270201 SUMMARY:Check this week: 2 changes\, soonest Feb 22 DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nFeb 22 · No tested fix yet\nUSGS WaterServices shut down\nhttps://cybern ative.ai/breakage-calendar/#2027-02-22-usgs-waterservices-decommissioned\n \nMar 15 · No tested fix yet\nTLS certificate maximum drops to 100 days\n https://cybernative.ai/breakage-calendar/#2027-03-15-tls-100-day-certifica tes\n\nThe whole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20270201@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20270201 DTEND;VALUE=DATE:20270208 SUMMARY:Check this week: 2 changes\, soonest Feb 22 DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nFeb 22 · No tested fix yet\nUSGS WaterServices shut down\nhttps://cybern ative.ai/breakage-calendar/#2027-02-22-usgs-waterservices-decommissioned\n \nMar 15 · No tested fix yet\nTLS certificate maximum drops to 100 days\n https://cybernative.ai/breakage-calendar/#2027-03-15-tls-100-day-certifica tes\n\nThe whole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20270208@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20270208 DTEND;VALUE=DATE:20270215 SUMMARY:Check this week: 2 changes\, soonest Feb 22 DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nFeb 22 · No tested fix yet\nUSGS WaterServices shut down\nhttps://cybern ative.ai/breakage-calendar/#2027-02-22-usgs-waterservices-decommissioned\n \nMar 15 · No tested fix yet\nTLS certificate maximum drops to 100 days\n https://cybernative.ai/breakage-calendar/#2027-03-15-tls-100-day-certifica tes\n\nThe whole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20270215@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20270215 DTEND;VALUE=DATE:20270222 SUMMARY:Check this week: 2 changes\, soonest Feb 22 DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nFeb 22 · No tested fix yet\nUSGS WaterServices shut down\nhttps://cybern ative.ai/breakage-calendar/#2027-02-22-usgs-waterservices-decommissioned\n \nMar 15 · No tested fix yet\nTLS certificate maximum drops to 100 days\n https://cybernative.ai/breakage-calendar/#2027-03-15-tls-100-day-certifica tes\n\nThe whole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20270222@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20270222 DTEND;VALUE=DATE:20270301 SUMMARY:Check this week: 2 changes\, soonest Feb 22 DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nFeb 22 · No tested fix yet\nUSGS WaterServices shut down\nhttps://cybern ative.ai/breakage-calendar/#2027-02-22-usgs-waterservices-decommissioned\n \nMar 15 · No tested fix yet\nTLS certificate maximum drops to 100 days\n https://cybernative.ai/breakage-calendar/#2027-03-15-tls-100-day-certifica tes\n\nThe whole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20270301@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20270301 DTEND;VALUE=DATE:20270308 SUMMARY:Check this week: TLS certificate maximum drops to 100 days (Mar 15) DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nMar 15 · No tested fix yet\nTLS certificate maximum drops to 100 days\nh ttps://cybernative.ai/breakage-calendar/#2027-03-15-tls-100-day-certificat es\n\nThe whole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20270308@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20270308 DTEND;VALUE=DATE:20270315 SUMMARY:Check this week: TLS certificate maximum drops to 100 days (Mar 15) DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nMar 15 · No tested fix yet\nTLS certificate maximum drops to 100 days\nh ttps://cybernative.ai/breakage-calendar/#2027-03-15-tls-100-day-certificat es\n\nThe whole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:week-20270315@cybernative.ai DTSTAMP:20261018T000000Z DTSTART;VALUE=DATE:20270315 DTEND;VALUE=DATE:20270322 SUMMARY:Check this week: TLS certificate maximum drops to 100 days (Mar 15) DESCRIPTION:Dates coming up that are worth checking now\, soonest first. Ea ch link says who is affected\, how to check and whether there is a fix.\n\ nMar 15 · No tested fix yet\nTLS certificate maximum drops to 100 days\nh ttps://cybernative.ai/breakage-calendar/#2027-03-15-tls-100-day-certificat es\n\nThe whole calendar: https://cybernative.ai/breakage-calendar/ URL:https://cybernative.ai/breakage-calendar/ TRANSP:TRANSPARENT END:VEVENT END:VCALENDAR