CHANGE LOG
Lifecycle changes
Reviewed changes to published lifecycle records. Layout edits and unchanged source checks are excluded.
| Date | Type | Record | Verified change | Evidence |
|---|---|---|---|---|
| official-source-efc9eb4e196ea12fca9948c6 | Source Change | Google Gemini API Models gemini-2.0-flash-lite-preview | Updated Google Gemini API Models gemini-2.0-flash-lite-preview from its verified official lifecycle source.{"cells": ["gemini-2.0-flash-lite-preview", "February 5, 2025", "December 9, 2025", "gemini-2.5-flash-lite"], "coverage_target": "google-gemini-api-models", "headers": ["Model", "Release date", "Shutdown date", "Recommended replacement"], "phases": [{"date_precision": "day", "ends_on": "2025-12-09", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "Shutdown date"}, "releaseCycle": {"column": "Model"}, "releaseDate": {"column": "Release date"}}} → {"cells": ["gemini-2.0-flash-lite-preview", "February 5, 2025", "December 9, 2025", "gemini-3.1-flash-lite"], "coverage_target": "google-gemini-api-models", "headers": ["Model", "Release date", "Shutdown date", "Recommended replacement"], "phases": [{"date_precision": "day", "ends_on": "2025-12-09", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "Shutdown date"}, "releaseCycle": {"column": "Model"}, "releaseDate": {"column": "Release date"}}}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Google Gemini API Models official lifecycle source |
| official-source-9d28c801e9394627adf26c54 | Source Change | DuckDB 1.5.0 | Updated DuckDB 1.5.0 from its verified official lifecycle source.{"cells": ["", "2026-03-09", "1.5.0", "Variegata (Tadorna variegata)", "2026-11-01"], "coverage_target": "duckdb", "headers": ["", "Date", "Version", "Codename (named after)", "End of life"], "phases": [{"date_precision": "day", "ends_on": "2026-11-01", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of life"}, "releaseCycle": {"column": "Version"}, "releaseDate": {"column": "Date"}}} → {"cells": ["", "2026-03-09", "1.5.0", "Variegata (Tadorna variegata)", "2027-03-01"], "coverage_target": "duckdb", "headers": ["", "Date", "Version", "Codename (named after)", "End of life"], "phases": [{"date_precision": "day", "ends_on": "2027-03-01", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of life"}, "releaseCycle": {"column": "Version"}, "releaseDate": {"column": "Date"}}}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | DuckDB official lifecycle source |
| official-source-38764dec84d3db723ce97e4c | Source Change | Snowflake Connector for Spark 2.14.0 | Updated Snowflake Connector for Spark 2.14.0 from its verified official lifecycle source.{"cells": ["", "Snowflake Connector for Spark", "3.2.2 (or later)", "2.14.0", "Release Notes", "Drivers and Libraries page"], "header": "Type | Client | Recommended Version | Minimum Supported Version (as of Feb 01, 2026, unless otherwise noted) [1] [2] | Release Information | Where to Download the Installers [3]", "recommended_version": "3.2.2 (or later)"} → {"cells": ["", "Snowflake Connector for Spark", "3.2.3 (or later)", "2.14.0", "Release Notes", "Drivers and Libraries page"], "header": "Type | Client | Recommended Version | Minimum Supported Version (as of Feb 01, 2026, unless otherwise noted) [1] [2] | Release Information | Where to Download the Installers [3]", "recommended_version": "3.2.3 (or later)"}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Snowflake lifecycle discovery |
| official-source-13ccdf66af5835b29cef81af | Source Change | Nuxt 2 | Updated Nuxt 2 from its verified official lifecycle source.{"cells": ["2.x (unsupported)", "", "2018-09-21", "2024-06-30", "v2.nuxt.com"], "coverage_target": "nuxt", "headers": ["Release", "", "Initial release", "End Of Life", "Docs"], "phases": [{"date_precision": "day", "ends_on": "2024-06-30", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End Of Life", "regex": "^(?P<value>\\d+-\\d+-\\d+).*$"}, "releaseCycle": {"column": "Release", "regex": "^(?P<value>\\d+)\\.x.*$"}, "releaseDate": {"column": "Initial release"}}} → {"cells": ["2.x (unsupported)", "", "2018-09-21", "2024-06-30", "nuxt.com"], "coverage_target": "nuxt", "headers": ["Release", "", "Initial release", "End Of Life", "Docs"], "phases": [{"date_precision": "day", "ends_on": "2024-06-30", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End Of Life", "regex": "^(?P<value>\\d+-\\d+-\\d+).*$"}, "releaseCycle": {"column": "Release", "regex": "^(?P<value>\\d+)\\.x.*$"}, "releaseDate": {"column": "Initial release"}}}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Nuxt official lifecycle source |
| official-source-1c2155ae0fa67a26d03d043a | Source Change | Metabase 58 (LTS) | Updated Metabase 58 (LTS) from its verified official lifecycle source.{"cells": ["Metabase 58 (LTS)", "December 17, 2025", "February 17, 2027", "58.35 September 30, 2026 EOL"], "coverage_target": "metabase", "headers": ["Version", "Released", "End of life", "Latest release"], "phases": [{"date_precision": "day", "ends_on": "2027-02-17", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of life"}, "releaseCycle": {"column": "Version", "regex": "^Metabase (?P<value>.+)$"}, "releaseDate": {"column": "Released"}}} → {"cells": ["Metabase 58 (LTS)", "December 17, 2025", "February 17, 2027", "58.37 October 20, 2026 EOL"], "coverage_target": "metabase", "headers": ["Version", "Released", "End of life", "Latest release"], "phases": [{"date_precision": "day", "ends_on": "2027-02-17", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of life"}, "releaseCycle": {"column": "Version", "regex": "^Metabase (?P<value>.+)$"}, "releaseDate": {"column": "Released"}}}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Metabase official lifecycle source |
| official-source-d6d1e6f70989fe32b777ce5e | Source Change | Metabase 63 | Updated Metabase 63 from its verified official lifecycle source.{"cells": ["Metabase 63", "July 7, 2026", "November 1, 2026", "63.19 September 30, 2026 EOL"], "coverage_target": "metabase", "headers": ["Version", "Released", "End of life", "Latest release"], "phases": [{"date_precision": "day", "ends_on": "2026-11-01", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of life"}, "releaseCycle": {"column": "Version", "regex": "^Metabase (?P<value>.+)$"}, "releaseDate": {"column": "Released"}}} → {"cells": ["Metabase 63", "July 7, 2026", "November 1, 2026", "63.21 October 20, 2026 EOL"], "coverage_target": "metabase", "headers": ["Version", "Released", "End of life", "Latest release"], "phases": [{"date_precision": "day", "ends_on": "2026-11-01", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of life"}, "releaseCycle": {"column": "Version", "regex": "^Metabase (?P<value>.+)$"}, "releaseDate": {"column": "Released"}}}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Metabase official lifecycle source |
| official-source-b4e8b2ba84758ad769b3f948 | Source Change | Metabase 64 (LTS) | Updated Metabase 64 (LTS) from its verified official lifecycle source.{"cells": ["Metabase 64 (LTS)", "September 16, 2026", "December 1, 2027", "64.1 October 6, 2026 EOL"], "coverage_target": "metabase", "headers": ["Version", "Released", "End of life", "Latest release"], "phases": [{"date_precision": "day", "ends_on": "2027-12-01", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of life"}, "releaseCycle": {"column": "Version", "regex": "^Metabase (?P<value>.+)$"}, "releaseDate": {"column": "Released"}}} → {"cells": ["Metabase 64 (LTS)", "September 16, 2026", "December 1, 2027", "64.3 October 20, 2026 EOL"], "coverage_target": "metabase", "headers": ["Version", "Released", "End of life", "Latest release"], "phases": [{"date_precision": "day", "ends_on": "2027-12-01", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of life"}, "releaseCycle": {"column": "Version", "regex": "^Metabase (?P<value>.+)$"}, "releaseDate": {"column": "Released"}}}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Metabase official lifecycle source |
| official-source-a2b1ebe05f7d1d409b083bac | Source Change | Snowflake Connector for Python 3.12.3 (as of Sep 30, 2026) | Updated Snowflake Connector for Python 3.12.3 (as of Sep 30, 2026) from its verified official lifecycle source.{"cells": ["", "Snowflake Connector for Python", "4.8.0 (or later)", "3.12.3 (as of Sep 30, 2026)", "Release Notes", "Drivers and Libraries page [3]"], "header": "Type | Client | Recommended Version | Minimum Supported Version (as of Feb 01, 2026, unless otherwise noted) [1] [2] | Release Information | Where to Download the Installers [3]", "recommended_version": "4.8.0 (or later)"} → {"cells": ["", "Snowflake Connector for Python", "5.1.0 (or later)", "3.12.3 (as of Sep 30, 2026)", "Release Notes", "Drivers and Libraries page [3]"], "header": "Type | Client | Recommended Version | Minimum Supported Version (as of Feb 01, 2026, unless otherwise noted) [1] [2] | Release Information | Where to Download the Installers [3]", "recommended_version": "5.1.0 (or later)"}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Snowflake lifecycle discovery |
| official-source-d414ee621170e9bdcec8db03 | Source Change | Snowflake PHP PDO Driver 3.0.3 (as of October 2, 2026) | Updated Snowflake PHP PDO Driver 3.0.3 (as of October 2, 2026) from its verified official lifecycle source.{"cells": ["", "PHP PDO Driver", "4.3.0 (or later)", "3.0.3 (as of October 2, 2026)", "Release Notes", "Drivers and Libraries page"], "header": "Type | Client | Recommended Version | Minimum Supported Version (as of Feb 01, 2026, unless otherwise noted) [1] [2] | Release Information | Where to Download the Installers [3]", "recommended_version": "4.3.0 (or later)"} → {"cells": ["", "PHP PDO Driver", "4.3.1 (or later)", "3.0.3 (as of October 2, 2026)", "Release Notes", "Drivers and Libraries page"], "header": "Type | Client | Recommended Version | Minimum Supported Version (as of Feb 01, 2026, unless otherwise noted) [1] [2] | Release Information | Where to Download the Installers [3]", "recommended_version": "4.3.1 (or later)"}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Snowflake lifecycle discovery |
| official-source-db31310f1b7f3e416b6042b2 | Source Change | Rocket.Chat Lifecycle policy | Updated Rocket.Chat Lifecycle policy from its verified official lifecycle source.{"coverage_target": "rocket-chat", "text": "To update your MongoDB version, visit Review and update MongoDB guide . | You can bypass the MongoDB version check by using the environment variable BYPASS_MONGO_VALIDATION=true . Bear in mind that this work around should be used only when necessary and may prevent some functionalities to work properly or even prevent the server to start. | Client app requirements | Before the Rocket.Chat mobile app version reaches its end-of-life (EOL), it's crucial to upgrade to ensure you continue to receive official support and have the latest security features. This is particularly important for white-label app users, as they might not receive automatic updates. Ensure you follow the version support dates to maintain optimum app performance and security standards. | The list of supported software for browsers, desktop, and mobile apps can be found in the Minimum Requirements for Client Apps document. | Workspace monitoring and logs | Monitoring is required for all supported installations. Refer to Monitor Workspace Logs and Metrics to learn more about the recommended observability stack which uses Prometheus, Grafana and Loki ."} → {"coverage_target": "rocket-chat", "text": "Ensure that your workspaces are updated to the latest stable versions. | Rocket.Chat provides two support windows depending on the release type: standard releases are supported for six months after their release date, while Long-Term Support (LTS) releases (starting with 7.10.x) are supported for 12 months. Once this period expires, hosted services such as the Push Gateway and Marketplace will cease to function for that particular version. During the support window, Rocket.Chat focuses on delivering security patches and responding to support queries concerning configuration and usage for the versions specified. Any bugs that are not security-related will be addressed solely in future releases. | Important references : | Supported versions and end-of-life schedule : Verify the final support date of each release version. | Supported versions and end-of-life schedule : Verify the final support date of each release version. | Release Lifecycle : Learn about Rocket.Chat’s release types and lifecycle. | Release Lifecycle : Learn about Rocket.Chat’s release types and lifecycle."}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Rocket.Chat official lifecycle source |
| official-source-15e7dd32a5518c935e997933 | Source Change | Red Hat Ansible Automation Platform Lifecycle policy | Updated Red Hat Ansible Automation Platform Lifecycle policy from its verified official lifecycle source.{"coverage_target": "red-hat-ansible-automation-platform", "text": "Versioning and Release Strategy for Ansible Engineering Maintained Certified Collections | Ansible Automation Platform Documentation | Ansible Automation Platform Release Notes | Ansible Automation Platform Preview and Deprecated Features | Ansible Automation Platform Self-Service Portal | Overview Life Cycle Dates Life Cycle Phases Ansible Automation Platform Installation Requirements Scope of Support Ansible Core Version Support by OS and Execution Environment Images Ansible Collections Configuration as Code Ansible Collection Requirements MCP Servers Lifecycle Postgres Database Scope of Support Versioning and Release Strategy for Ansible Engineering Maintained Certified Collections Ansible Automation Platform Documentation Ansible Automation Platform Release Notes Ansible Automation Platform Preview and Deprecated Features Ansible Automation Platform Self-Service Portal | Ansible Automation Platform Lifecycle"} → {"coverage_target": "red-hat-ansible-automation-platform", "text": "Versioning and Release Strategy for Ansible Engineering Maintained Certified Collections | Ansible Automation Platform Documentation | Ansible Automation Platform Release Notes | Ansible Automation Platform Preview and Deprecated Features | Ansible Automation Portal | Overview Life Cycle Dates Life Cycle Phases Ansible Automation Platform Installation Requirements Scope of Support Ansible Core Version Support by OS and Execution Environment Images Ansible Collections Configuration as Code Ansible Collection Requirements MCP Servers Lifecycle Postgres Database Scope of Support Versioning and Release Strategy for Ansible Engineering Maintained Certified Collections Ansible Automation Platform Documentation Ansible Automation Platform Release Notes Ansible Automation Platform Preview and Deprecated Features Ansible Automation Portal | Ansible Automation Platform Lifecycle"}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Red Hat Ansible Automation Platform official lifecycle source |
| official-source-a640ef21e365ca7daf1b978f | Source Change | Quarkus Lifecycle policy | Updated Quarkus Lifecycle policy from its verified official lifecycle source.{"coverage_target": "quarkus-framework", "text": "Why follow this process | Due to the sensitive nature of security bugs, the disclosure process is more constrained than a regular bug. We appreciate you following these industry accepted guidelines, which gives time for a proper fix and limit the time window of attack. | Supported Versions | The community will fix security bugs for the latest major.minor version published at https://quarkus.io/get-started/ . | Latest 3.x"} → {"coverage_target": "quarkus-framework", "text": "We start assessing a report only once it includes a reproducer that demonstrates the issue. Without one, we ask for it and do not treat the report as a vulnerability. If no reproducer arrives within 14 days, we close the report. | A valid reproducer: | Runs on a specific version. It targets the Quarkus version stated in the report. We prioritize issues that reproduce on a supported version or a recent commit on main . An issue that only reproduces on an End-of-Life version still gets a CVE, but is unlikely to be fixed. | Runs on a specific version. It targets the Quarkus version stated in the report. We prioritize issues that reproduce on a supported version or a recent commit on main . An issue that only reproduces on an End-of-Life version still gets a CVE, but is unlikely to be fixed. | Is source code. A minimal Quarkus application, a test case, or a script, sent as a private Git repository, a zip of the sources, or a patch. We do not run binaries, container images, or obfuscated code."}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Quarkus official lifecycle source |
| official-source-78f7b83dbca131b0412401f6 | Source Change | Snowflake PHP PDO Driver 3.0.3 (as of October 2, 2026) | Updated Snowflake PHP PDO Driver 3.0.3 (as of October 2, 2026) from its verified official lifecycle source.{"cells": ["", "PHP PDO Driver", "4.2.0 (or later)", "3.0.3 (as of October 2, 2026)", "Release Notes", "Drivers and Libraries page"], "header": "Type | Client | Recommended Version | Minimum Supported Version (as of Feb 01, 2026, unless otherwise noted) [1] [2] | Release Information | Where to Download the Installers [3]", "recommended_version": "4.2.0 (or later)"} → {"cells": ["", "PHP PDO Driver", "4.3.0 (or later)", "3.0.3 (as of October 2, 2026)", "Release Notes", "Drivers and Libraries page"], "header": "Type | Client | Recommended Version | Minimum Supported Version (as of Feb 01, 2026, unless otherwise noted) [1] [2] | Release Information | Where to Download the Installers [3]", "recommended_version": "4.3.0 (or later)"}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Snowflake lifecycle discovery |
| official-source-36361768727040e2d2590487 | Source Change | Snowflake ODBC Driver 3.5.0 (as of October 2, 2026) | Updated Snowflake ODBC Driver 3.5.0 (as of October 2, 2026) from its verified official lifecycle source.{"cells": ["", "ODBC Driver", "4.0.0 (or later)", "3.5.0 (as of October 2, 2026)", "Release Notes", "ODBC Download page"], "header": "Type | Client | Recommended Version | Minimum Supported Version (as of Feb 01, 2026, unless otherwise noted) [1] [2] | Release Information | Where to Download the Installers [3]", "recommended_version": "4.0.0 (or later)"} → {"cells": ["", "ODBC Driver", "4.2.0 (or later)", "3.5.0 (as of October 2, 2026)", "Release Notes", "ODBC Download page"], "header": "Type | Client | Recommended Version | Minimum Supported Version (as of Feb 01, 2026, unless otherwise noted) [1] [2] | Release Information | Where to Download the Installers [3]", "recommended_version": "4.2.0 (or later)"}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Snowflake lifecycle discovery |
| official-source-5ce11be89f695ae57d036c5a | Source Change | Node.js Lifecycle policy | Updated Node.js Lifecycle policy from its verified official lifecycle source.{"coverage_target": "nodejs", "text": "Installation methods designated as “Official” must meet the following requirements: | Community Installation Methods | Community installation methods included on the self-service download page (located at /download) must also adhere to a minimum set of criteria: | Version Support: Must support all currently supported, non-End-of-Life (EOL) Node.js versions. | OS Compatibility: Must function on at least one officially supported Operating System (OS). | For example, an installation method claiming compatibility with “Windows” must function on “Windows 10”, “Windows 11”, and all their editions (including server versions). | Similarly, an installation method claiming compatibility with “Linux” must be installable on all major Linux distributions, not just a specific subset. It cannot rely on distribution-specific package managers like apt or dnf ."} → {"coverage_target": "nodejs", "text": "“Recommended” methods allow developers to install and use multiple versions of Node.js on a system concurrently. | “Recommended” methods have a close relationship with the Node.js project, including direct communication channels. | “Community” methods are additional installation methods also available on the Downloads page, and meet the following criteria: | “Community” methods must support all currently supported, non-End-of-Life (EOL) Node.js versions. | “Community” methods must function on at least one officially supported Operating System (OS), and must not be limited to a subset of OS distributions or versions. | “Community” methods must be free to use and open source, must not be sold as a commercial product, and must not be a paid service. | Release Schedule"}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Node.js official lifecycle source |
| official-source-a5aa219bbc18d99f7ae6471b | Source Change | Kubernetes Node Feature Discovery Lifecycle policy | Updated Kubernetes Node Feature Discovery Lifecycle policy from its verified official lifecycle source.{"coverage_target": "kubernetes-node-feature-discovery", "text": "Action Required / Behavior Changes | nfd-topology-updater RBAC ( #2509 ): the ClusterRole needs list + watch on pods (was get only). Helm and kustomize manifests ship the update, but deployments that bump only the image will crash-loop with pods is forbidden ... cannot list resource \"pods\" until the new RBAC is applied. | NodeFeatureRule templates ( #2507 ): env , expandenv and getHostByName were removed from the available template functions (security hardening). Templates using them now fail to parse ( function \"env\" not defined ); the rule is skipped and an error is logged. | Helm worker updateStrategy default ( #2519 ): now rollingUpdate: {maxUnavailable: \"10%\"} (was Kubernetes default 1 ). Note for type: OnDelete users: the chart's default rollingUpdate block is deep-merged into your values; the API server accepts and ignores it (verified on v1.30). Optionally set worker.updateStrategy.rollingUpdate: null for a clean spec. | resyncPeriod (nfd-master): drives both the informer resync and the (new in this release, #2415 ) periodic full reconcile that re-applies labels and cleans up drift. Setting it to 0 disables this safety net entirely."} → {"coverage_target": "kubernetes-node-feature-discovery", "text": "Helm: set metadata.namespace on the PodMonitor. When the chart is rendered through Kustomize's Helm integration (Kustomize 5.8 and later), the PodMonitor had no namespace and Argo CD refused to sync it with InvalidSpecError: Namespace for ... PodMonitor is missing ( #2577 , fixes #2576 ). | Helm: render priorityClassName once in the nfd-worker pod spec. With both the top-level priorityClassName and worker.priorityClassName set, the key was emitted twice and the effective value depended on the YAML decoder; worker.priorityClassName now takes precedence and falls back to the top-level value. The nfd-gc container securityContext is now configurable with gc.securityContext , which defaults to the previously hardcoded settings ( #2624 , fixes #2622 ). | kustomize: the prune overlay works again. It removed /rules/1 from the nfd-master ClusterRole with a JSON patch, and since v0.17.0 that index is the nodes rule, so the prune Job failed with nodes is forbidden: ... cannot list resource \"nodes\" and left all NFD labels, annotations and extended resources on the nodes ( #2607 ). | nfd-master: NodeFeatureGroup status lists member nodes by Node name. It used the system.name feature's nodename element, so nodes whose features came only from third-party NodeFeature objects were listed with an empty name ( #2621 ). | nfd-master: NodeFeatureGroups outside nfd-master's own namespace get their status populated. The update queue was keyed by object name only, so same-name NodeFeatureGroups in different namespaces collided, and the lookup and status write were pinned to nfd-master's namespace ( #2559 )."}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Kubernetes Node Feature Discovery official lifecycle source |
| official-source-0c4e2588462f1558d95c6262 | Source Change | Snowflake .NET Driver 4.2.0 (as of October 2, 2026) | Updated Snowflake .NET Driver 4.2.0 (as of October 2, 2026) from its verified official lifecycle source.{"cells": ["Connectors and Drivers", ".NET Driver", "6.3.0 (or later)", "4.2.0 (as of October 2, 2026)", "Release Notes", "Drivers and Libraries page"], "header": "Type | Client | Recommended Version | Minimum Supported Version (as of Feb 01, 2026, unless otherwise noted) [1] [2] | Release Information | Where to Download the Installers [3]", "recommended_version": "6.3.0 (or later)"} → {"cells": ["Connectors and Drivers", ".NET Driver", "6.4.0 (or later)", "4.2.0 (as of October 2, 2026)", "Release Notes", "Drivers and Libraries page"], "header": "Type | Client | Recommended Version | Minimum Supported Version (as of Feb 01, 2026, unless otherwise noted) [1] [2] | Release Information | Where to Download the Installers [3]", "recommended_version": "6.4.0 (or later)"}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Snowflake lifecycle discovery |
| official-source-59765cc66aeca708301879f8 | Source Change | Cloud Service Mesh support for the in-cluster ISTIOD control plane on Google Kubernetes Engine (GKE) on Google Cloud Published lifecycle | Updated Cloud Service Mesh support for the in-cluster ISTIOD control plane on Google Kubernetes Engine (GKE) on Google Cloud Published lifecycle from its verified official lifecycle source.{"text": ["To retain export capabilities, assign the Cloud SQL Editor ( roles/cloudsql.editor ) role or update custom roles to include the cloudsql.instances.export permission.", "For more information, see Cloud SQL roles .", "Cloud Service Mesh", "Deprecated", "Cloud Service Mesh support for the in-cluster ISTIOD control plane on Google Kubernetes Engine (GKE) on Google Cloud is deprecated as of September 28, 2026, and support will end on March 1, 2028 . After March 1, 2028, in-cluster control plane components on GKE will not receive updates, security patches, or support from Google Cloud.", "Cloud Service Mesh with the in-cluster ISTIOD control plane on Google Distributed Cloud (software only) continues to be supported as described in Supported platforms .", "You must migrate your clusters to managed Cloud Service Mesh by March 1, 2028. review the Supported features to confirm feature compatibility, and follow the migration guide to transition to managed Cloud Service Mesh with the TRAFFIC_DIRECTOR control plane.", "For more details on the deprecation schedule, see Deprecations ."]} → {"text": ["Check your compatibility. Review the Supported features to confirm feature compatibility with the TRAFFIC_DIRECTOR control plane and evaluate a fleet's compatibility for control plane modernization .", "Plan your modernization following the modernization guide .", "For more details on the transition, see Managed control plane documentation and monitor the release notes for ongoing updates.", "Deprecated", "Cloud Service Mesh support for the in-cluster ISTIOD control plane on Google Kubernetes Engine (GKE) on Google Cloud is deprecated as of September 28, 2026, and support will end on March 1, 2028 . After March 1, 2028, in-cluster control plane components on GKE will not receive updates, security patches, or support from Google Cloud.", "Cloud Service Mesh with the in-cluster ISTIOD control plane on Google Distributed Cloud (software only) continues to be supported as described in Supported platforms .", "You must migrate your clusters to managed Cloud Service Mesh by March 1, 2028. review the Supported features to confirm feature compatibility, and follow the migration guide to transition to managed Cloud Service Mesh with the TRAFFIC_DIRECTOR control plane.", "For more details on the deprecation schedule, see Deprecations ."]}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Alphabet (Google) lifecycle discovery |
| official-source-cd0d15139db0c440c29f8758 | Source Change | Cloud Service Mesh support for the managed ISTIOD control plane on Google Kubernetes Engine (GKE) on Google Cloud Published lifecycle | Updated Cloud Service Mesh support for the managed ISTIOD control plane on Google Kubernetes Engine (GKE) on Google Cloud Published lifecycle from its verified official lifecycle source.{"text": ["Cloud Service Mesh with the in-cluster ISTIOD control plane on Google Distributed Cloud (software only) continues to be supported as described in Supported platforms .", "You must migrate your clusters to managed Cloud Service Mesh by March 1, 2028. review the Supported features to confirm feature compatibility, and follow the migration guide to transition to managed Cloud Service Mesh with the TRAFFIC_DIRECTOR control plane.", "For more details on the deprecation schedule, see Deprecations .", "Deprecated", "Cloud Service Mesh support for the managed ISTIOD control plane on Google Kubernetes Engine (GKE) on Google Cloud is deprecated as of September 28, 2026, and support will end on March 1, 2028 . After March 1, 2028, managed ISTIOD control plane components on GKE on Google Cloud will not receive updates, security patches, or support from Google Cloud, and workload sidecars on unmodernized clusters will fail and be unable to receive or send requests.", "Google Cloud is transitioning managed Cloud Service Mesh with Istio APIs to the TRAFFIC_DIRECTOR control plane implementation using Istio APIs. As part of this transition, support will also end for any features that are incompatible with the TRAFFIC_DIRECTOR control plane.", "To continue using managed Cloud Service Mesh on GKE, you must modernize your clusters by March 1, 2028:", "Confirm that you affected."]} → {"text": ["To retain export capabilities, assign the Cloud SQL Editor ( roles/cloudsql.editor ) role or update custom roles to include the cloudsql.instances.export permission.", "For more information, see Cloud SQL roles .", "Cloud Service Mesh", "Deprecated", "Cloud Service Mesh support for the managed ISTIOD control plane on Google Kubernetes Engine (GKE) on Google Cloud is deprecated as of September 28, 2026, and support will end on March 1, 2028 . After March 1, 2028, managed ISTIOD control plane components on GKE on Google Cloud will not receive updates, security patches, or support from Google Cloud, and workload sidecars on unmodernized clusters will fail and be unable to receive or send requests.", "Google Cloud is transitioning managed Cloud Service Mesh with Istio APIs to the TRAFFIC_DIRECTOR control plane implementation using Istio APIs. As part of this transition, support will also end for any features that are incompatible with the TRAFFIC_DIRECTOR control plane.", "To continue using managed Cloud Service Mesh on GKE, you must modernize your clusters by March 1, 2028:", "Confirm that you affected."]}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | Alphabet (Google) lifecycle discovery |
| official-source-1c6fa6348a68f2c086f163a2 | Source Change | CakePHP Lifecycle policy | Updated CakePHP Lifecycle policy from its verified official lifecycle source.{"coverage_target": "cakephp", "text": "4.6 Roadmap | 4.5 Roadmap | 4.4 Roadmap | 4.x End of Life | Release bug fixes until September 10 2025 (24 months after 5.0.0). | Release security fixes until CakePHP 6.0 has been released (TBD). | 3.x End of Life"} → {"coverage_target": "cakephp", "text": "4.6 Roadmap | 4.5 Roadmap | 4.4 Roadmap | 4.x End of Life | Release bug fixes until September 10 2025 (24 months after 5.0.0). 4.6 continues to receive bug fixes until CakePHP 6.0 has been released. | Release security fixes until CakePHP 6.0 has been released (TBD). | 3.x End of Life"}Automatically verified because the normalized lifecycle record came from its registered primary-source route, remained structurally valid and did not conflict with another active record. | CakePHP official lifecycle source |