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-abc10deb5ad67fba27de5282 | Source Change | Veeam ONE 12 | Updated Veeam ONE 12 from its verified official lifecycle source.{"cells": ["", "12", "February 2023", "November 2025", "February 2027"], "coverage_target": "veeam-one", "headers": ["Product", "Version", "Release Date", "End of Fix", "End of Support and Security Fix"]} → {"cells": ["Veeam ONE", "", "12", "February 2023", "September 2025", "February 2027"], "coverage_target": "veeam-one", "headers": ["Product", "Version", "Release Date", "End of Fix", "End of Support and Security Fix"]}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. | Veeam Backup & Replication official lifecycle source |
| official-source-2c25feae77cf96c21628af4d | Source Change | Veeam Backup for Microsoft 365 7 | Updated Veeam Backup for Microsoft 365 7 from its verified official lifecycle source.{"cells": ["", "7", "December 2023", "November 2025", "February 2027"], "coverage_target": "veeam-backup-for-microsoft-365", "headers": ["Product", "Version", "Release Date", "End of Fix", "End of Support and Security Fix"]} → {"cells": ["Veeam Backup for Microsoft 365", "", "7", "February 2023", "December 2023", "June 2025"], "coverage_target": "veeam-backup-for-microsoft-365", "headers": ["Product", "Version", "Release Date", "End of Fix", "End of Support and Security Fix"]}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. | Veeam Backup & Replication official lifecycle source |
| official-source-93923e9b03552126cde3ec8f | Source Change | Veeam Backup for Microsoft 365 8 | Updated Veeam Backup for Microsoft 365 8 from its verified official lifecycle source.{"cells": ["", "8", "December 2023", "September 2025", "December 2026"], "coverage_target": "veeam-backup-for-microsoft-365", "headers": ["Product", "Version", "Release Date", "End of Fix", "End of Support and Security Fix"]} → {"cells": ["Veeam Backup for Microsoft 365", "8", "September 2024", "Next GA Date", "May 2027"], "coverage_target": "veeam-backup-for-microsoft-365", "headers": ["Product", "Version", "Release Date", "End of Fix", "End of Support and Security Fix"]}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. | Veeam Backup & Replication official lifecycle source |
| official-source-a4edf4ebdb0c81e9ebf3040e | Source Change | Veeam Backup & Replication 11 | Updated Veeam Backup & Replication 11 from its verified official lifecycle source.{"cells": ["", "11", "February 2021", "February 2023", "February 2024"], "coverage_target": "veeam-backup-and-replication", "headers": ["Product", "Version", "Release Date", "End of Fix", "End of Support and Security Fix"]} → {"cells": ["Veeam Backup & Replication", "", "11", "February 2021", "February 2023", "February 2024"], "coverage_target": "veeam-backup-and-replication", "headers": ["Product", "Version", "Release Date", "End of Fix", "End of Support and Security Fix"]}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. | Veeam Backup & Replication official lifecycle source |
| official-source-835346ef570fabd1f49cb8b9 | Source Change | Veeam Backup & Replication 12 | Updated Veeam Backup & Replication 12 from its verified official lifecycle source.{"cells": ["", "12", "February 2023", "November 2025", "February 2027"], "coverage_target": "veeam-backup-and-replication", "headers": ["Product", "Version", "Release Date", "End of Fix", "End of Support and Security Fix"]} → {"cells": ["Veeam Backup & Replication", "", "12", "February 2023", "November 2025", "February 2027"], "coverage_target": "veeam-backup-and-replication", "headers": ["Product", "Version", "Release Date", "End of Fix", "End of Support and Security Fix"]}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. | Veeam Backup & Replication official lifecycle source |
| official-source-00d478c25231370ae8a13a89 | Source Change | MongoDB Server 3.0 | Updated MongoDB Server 3.0 from its verified official lifecycle source.{"cells": ["MongoDB 3.0", "March 2015", "February 28, 2018"]} → {"cells": ["MongoDB 3.0", "March 2015", "February 28, 2018"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2018-02-28", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-9e2ad9e619f91cd091f43ede | Source Change | MongoDB Server 3.2 | Updated MongoDB Server 3.2 from its verified official lifecycle source.{"cells": ["MongoDB 3.2", "December 2015", "September 30, 2018"]} → {"cells": ["MongoDB 3.2", "December 2015", "September 30, 2018"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2018-09-30", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-41eb6abe9720f3bbc1b497b5 | Source Change | MongoDB Server 3.4 | Updated MongoDB Server 3.4 from its verified official lifecycle source.{"cells": ["MongoDB 3.4", "November 2016", "January 31, 2020"]} → {"cells": ["MongoDB 3.4", "November 2016", "January 31, 2020"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2020-01-31", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-d365cfa69a7d18d6ca8ff3a1 | Source Change | MongoDB Server 3.6 | Updated MongoDB Server 3.6 from its verified official lifecycle source.{"cells": ["MongoDB 3.6", "November 2017", "April 30, 2021"]} → {"cells": ["MongoDB 3.6", "November 2017", "April 30, 2021"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2021-04-30", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-7d5ff2dace79b1a539ac1935 | Source Change | MongoDB Server 4.0 | Updated MongoDB Server 4.0 from its verified official lifecycle source.{"cells": ["MongoDB 4.0", "June 2018", "April 30, 2022"]} → {"cells": ["MongoDB 4.0", "June 2018", "April 30, 2022"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2022-04-30", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-bd141282a1fd5546b70adbec | Source Change | MongoDB Server 4.2 | Updated MongoDB Server 4.2 from its verified official lifecycle source.{"cells": ["MongoDB 4.2", "August 2019", "April 30, 2023"]} → {"cells": ["MongoDB 4.2", "August 2019", "April 30, 2023"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2023-04-30", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-090a40ee27bde1f2adfabfcf | Source Change | MongoDB Server 4.4 | Updated MongoDB Server 4.4 from its verified official lifecycle source.{"cells": ["MongoDB 4.4", "July 2020", "February 29, 2024"]} → {"cells": ["MongoDB 4.4", "July 2020", "February 29, 2024"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2024-02-29", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-577af9c2c23604c7531f7de1 | Source Change | MongoDB Server 5.1 | Updated MongoDB Server 5.1 from its verified official lifecycle source.{"cells": ["MongoDB 5.1", "November 2021", "January 19, 2022"]} → {"cells": ["MongoDB 5.1", "November 2021", "January 19, 2022"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2022-01-19", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-cbace292f1242b478a800f47 | Source Change | MongoDB Server 5.2 | Updated MongoDB Server 5.2 from its verified official lifecycle source.{"cells": ["MongoDB 5.2", "January 2022", "March 23, 2022"]} → {"cells": ["MongoDB 5.2", "January 2022", "March 23, 2022"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2022-03-23", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-11f0c68f76a7c1612d272ee4 | Source Change | MongoDB Server 5.3 | Updated MongoDB Server 5.3 from its verified official lifecycle source.{"cells": ["MongoDB 5.3", "March 2022", "July 19, 2022"]} → {"cells": ["MongoDB 5.3", "March 2022", "July 19, 2022"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2022-07-19", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-015aa47def73ef470e55613d | Source Change | MongoDB Server 6.1 | Updated MongoDB Server 6.1 from its verified official lifecycle source.{"cells": ["MongoDB 6.1", "October 2022", "February 9, 2023"]} → {"cells": ["MongoDB 6.1", "October 2022", "February 9, 2023"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2023-02-09", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-63944d82d99fbcf3019a046b | Source Change | MongoDB Server 6.2 | Updated MongoDB Server 6.2 from its verified official lifecycle source.{"cells": ["MongoDB 6.2", "February 2023", "April 24, 2023"]} → {"cells": ["MongoDB 6.2", "February 2023", "April 24, 2023"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2023-04-24", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-ce5fce9f7db79e75398944f3 | Source Change | MongoDB Server 6.3 | Updated MongoDB Server 6.3 from its verified official lifecycle source.{"cells": ["MongoDB 6.3", "April 2023", "August 31, 2023"]} → {"cells": ["MongoDB 6.3", "April 2023", "August 31, 2023"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2023-08-31", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-43d0ede1afde8f676fbf3721 | Source Change | MongoDB Server 7.1 | Updated MongoDB Server 7.1 from its verified official lifecycle source.{"cells": ["MongoDB 7.1", "October 2023", "January 23, 2024"]} → {"cells": ["MongoDB 7.1", "October 2023", "January 23, 2024"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2024-01-23", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |
| official-source-d6e467c7c1a587542f3f8e30 | Source Change | MongoDB Server 7.2 | Updated MongoDB Server 7.2 from its verified official lifecycle source.{"cells": ["MongoDB 7.2", "January 2024", "March 27, 2024"]} → {"cells": ["MongoDB 7.2", "January 2024", "March 27, 2024"], "coverage_target": "mongodb", "headers": ["Release", "Release Date", "End of Life Date"], "phases": [{"date_precision": "day", "ends_on": "2024-03-27", "label": "Support", "phase_type": "retirement", "sort_order": 0}], "registered_fields": {"eol": {"column": "End of Life Date"}, "releaseCycle": {"column": "Release", "regex": "^MongoDB (?P<value>\\d+\\.\\d+).*$"}, "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. | MongoDB lifecycle discovery |