feat: Increase required minimum versions to Postgres 15, PostGIS 3.3 (#9538)
BREAKING CHANGE: This releases increases the required minimum versions to Postgres `15`, PostGIS `3.3` and removes support for Postgres `13`, `14`, PostGIS `3.1`, `3.2`.
This commit is contained in:
20
.github/workflows/ci.yml
vendored
20
.github/workflows/ci.yml
vendored
@@ -213,23 +213,11 @@ jobs:
|
|||||||
strategy:
|
strategy:
|
||||||
matrix:
|
matrix:
|
||||||
include:
|
include:
|
||||||
- name: PostgreSQL 13, PostGIS 3.1
|
- name: PostgreSQL 15, PostGIS 3.3
|
||||||
POSTGRES_IMAGE: postgis/postgis:13-3.1
|
POSTGRES_IMAGE: postgis/postgis:15-3.3
|
||||||
NODE_VERSION: 22.12.0
|
NODE_VERSION: 22.12.0
|
||||||
- name: PostgreSQL 13, PostGIS 3.2
|
- name: PostgreSQL 15, PostGIS 3.4
|
||||||
POSTGRES_IMAGE: postgis/postgis:13-3.2
|
POSTGRES_IMAGE: postgis/postgis:15-3.4
|
||||||
NODE_VERSION: 22.12.0
|
|
||||||
- name: PostgreSQL 13, PostGIS 3.3
|
|
||||||
POSTGRES_IMAGE: postgis/postgis:13-3.3
|
|
||||||
NODE_VERSION: 22.12.0
|
|
||||||
- name: PostgreSQL 13, PostGIS 3.4
|
|
||||||
POSTGRES_IMAGE: postgis/postgis:13-3.4
|
|
||||||
NODE_VERSION: 22.12.0
|
|
||||||
- name: PostgreSQL 13, PostGIS 3.5
|
|
||||||
POSTGRES_IMAGE: postgis/postgis:13-3.5
|
|
||||||
NODE_VERSION: 22.12.0
|
|
||||||
- name: PostgreSQL 14, PostGIS 3.5
|
|
||||||
POSTGRES_IMAGE: postgis/postgis:14-3.5
|
|
||||||
NODE_VERSION: 22.12.0
|
NODE_VERSION: 22.12.0
|
||||||
- name: PostgreSQL 15, PostGIS 3.5
|
- name: PostgreSQL 15, PostGIS 3.5
|
||||||
POSTGRES_IMAGE: postgis/postgis:15-3.5
|
POSTGRES_IMAGE: postgis/postgis:15-3.5
|
||||||
|
|||||||
34
README.md
34
README.md
@@ -127,33 +127,33 @@ Before you start make sure you have installed:
|
|||||||
|
|
||||||
Parse Server is continuously tested with the most recent releases of Node.js to ensure compatibility. We follow the [Node.js Long Term Support plan](https://github.com/nodejs/Release) and only test against versions that are officially supported and have not reached their end-of-life date.
|
Parse Server is continuously tested with the most recent releases of Node.js to ensure compatibility. We follow the [Node.js Long Term Support plan](https://github.com/nodejs/Release) and only test against versions that are officially supported and have not reached their end-of-life date.
|
||||||
|
|
||||||
| Version | Minimum Version | End-of-Life | Compatible |
|
| Version | Minimum Version | End-of-Life | Parse Server Support |
|
||||||
|------------|-----------------|-------------|------------|
|
|------------|-----------------|-------------|----------------------|
|
||||||
| Node.js 18 | 18.20.4 | April 2025 | ✅ Yes |
|
| Node.js 18 | 18.20.4 | April 2025 | <= 8.x (2025) |
|
||||||
| Node.js 20 | 20.18.0 | April 2026 | ✅ Yes |
|
| Node.js 20 | 20.18.0 | April 2026 | <= 9.x (2026) |
|
||||||
| Node.js 22 | 22.12.0 | April 2027 | ✅ Yes |
|
| Node.js 22 | 22.12.0 | April 2027 | <= 10.x (2027) |
|
||||||
|
|
||||||
#### MongoDB
|
#### MongoDB
|
||||||
|
|
||||||
Parse Server is continuously tested with the most recent releases of MongoDB to ensure compatibility. We follow the [MongoDB support schedule](https://www.mongodb.com/support-policy) and [MongoDB lifecycle schedule](https://www.mongodb.com/support-policy/lifecycles) and only test against versions that are officially supported and have not reached their end-of-life date. MongoDB "rapid releases" are ignored as these are considered pre-releases of the next major version.
|
Parse Server is continuously tested with the most recent releases of MongoDB to ensure compatibility. We follow the [MongoDB support schedule](https://www.mongodb.com/support-policy) and [MongoDB lifecycle schedule](https://www.mongodb.com/support-policy/lifecycles) and only test against versions that are officially supported and have not reached their end-of-life date. MongoDB "rapid releases" are ignored as these are considered pre-releases of the next major version.
|
||||||
|
|
||||||
| Version | Minimum Version | End-of-Life | Compatible |
|
| Version | Minimum Version | End-of-Life | Parse Server Support |
|
||||||
|-----------|-----------------|-------------|------------|
|
|-----------|-----------------|-------------|----------------------|
|
||||||
| MongoDB 6 | 6.0.19 | July 2025 | ✅ Yes |
|
| MongoDB 6 | 6.0.19 | July 2025 | <= 8.x (2025) |
|
||||||
| MongoDB 7 | 7.0.16 | August 2026 | ✅ Yes |
|
| MongoDB 7 | 7.0.16 | August 2026 | <= 9.x (2026) |
|
||||||
| MongoDB 8 | 8.0.4 | TDB | ✅ Yes |
|
| MongoDB 8 | 8.0.4 | TDB | <= 10.x (2027) |
|
||||||
|
|
||||||
#### PostgreSQL
|
#### PostgreSQL
|
||||||
|
|
||||||
Parse Server is continuously tested with the most recent releases of PostgreSQL and PostGIS to ensure compatibility, using [PostGIS docker images](https://registry.hub.docker.com/r/postgis/postgis/tags?page=1&ordering=last_updated). We follow the [PostgreSQL support schedule](https://www.postgresql.org/support/versioning) and [PostGIS support schedule](https://www.postgis.net/eol_policy/) and only test against versions that are officially supported and have not reached their end-of-life date. Due to the extensive PostgreSQL support duration of 5 years, Parse Server drops support about 2 years before the official end-of-life date.
|
Parse Server is continuously tested with the most recent releases of PostgreSQL and PostGIS to ensure compatibility, using [PostGIS docker images](https://registry.hub.docker.com/r/postgis/postgis/tags?page=1&ordering=last_updated). We follow the [PostgreSQL support schedule](https://www.postgresql.org/support/versioning) and [PostGIS support schedule](https://www.postgis.net/eol_policy/) and only test against versions that are officially supported and have not reached their end-of-life date. Due to the extensive PostgreSQL support duration of 5 years, Parse Server drops support about 2 years before the official end-of-life date.
|
||||||
|
|
||||||
| Version | PostGIS Version | End-of-Life | Parse Server Support | Compatible |
|
| Version | PostGIS Version | End-of-Life | Parse Server Support |
|
||||||
|-------------|-------------------------|---------------|----------------------|------------|
|
|-------------|-------------------------|---------------|----------------------|
|
||||||
| Postgres 13 | 3.1, 3.2, 3.3, 3.4, 3.5 | November 2025 | <= 6.x (2023) | ✅ Yes |
|
| Postgres 13 | 3.1, 3.2, 3.3, 3.4, 3.5 | November 2025 | <= 6.x (2023) |
|
||||||
| Postgres 14 | 3.5 | November 2026 | <= 7.x (2024) | ✅ Yes |
|
| Postgres 14 | 3.5 | November 2026 | <= 7.x (2024) |
|
||||||
| Postgres 15 | 3.5 | November 2027 | <= 8.x (2025) | ✅ Yes |
|
| Postgres 15 | 3.3, 3.4, 3.5 | November 2027 | <= 8.x (2025) |
|
||||||
| Postgres 16 | 3.5 | November 2028 | <= 9.x (2026) | ✅ Yes |
|
| Postgres 16 | 3.5 | November 2028 | <= 9.x (2026) |
|
||||||
| Postgres 17 | 3.5 | November 2029 | <= 9.x (2026) | ✅ Yes |
|
| Postgres 17 | 3.5 | November 2029 | <= 10.x (2027) |
|
||||||
|
|
||||||
### Locally
|
### Locally
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user