Bump CI environment, remove Postgres 10 support (#7323)
* bumped MongoDB to 4.4.5 * bump Node to 14.16.1 * removed obsolete COVERAGE_OPTION * improved postges support note * bump more node * Remove MongoDB 3.6 support (EOL) (#7315) * removed mongodb 3.6 support * add changelog entry * updated CI check * bumped MongoDB to 4.4.5 * bump Node to 14.16.1 * removed obsolete COVERAGE_OPTION * improved postges support note * bump more node * updated package lock * Revert "bumped MongoDB to 4.4.5" This reverts commit ce9c8108c3deaec3bbe753faf5fdedbfec1e48c9. * skipping MongoDB 4.4.5 temporarily * fixed bug in CI check that did not consider ignored versions when checking for newer versions * removed Postgres 10 support * updated Postgres versions * renamed MongoDB CI tests * fixed Postgres compatibility table * fix Postgres badge
This commit is contained in:
35
README.md
35
README.md
@@ -19,7 +19,7 @@
|
||||
<a href="https://snyk.io/test/github/parse-community/parse-server"><img alt="Snyk badge" src="https://snyk.io/test/github/parse-community/parse-server/badge.svg"></a>
|
||||
<a href="https://nodejs.org/"><img alt="Node.js 12,14,15" src="https://img.shields.io/badge/nodejs-12,_14,_15-green.svg?logo=node.js&style=flat"></a>
|
||||
<a href="https://www.mongodb.com/"><img alt="MongoDB 4.0,4.2,4.4" src="https://img.shields.io/badge/mongodb-4.0,_4.2,_4.4-green.svg?logo=mongodb&style=flat"></a>
|
||||
<a href="https://www.postgresql.org"> <img alt="PostgreSQL 10,11,12,13" src="https://img.shields.io/badge/postgresql-10,_11,_12,_13-green.svg?logo=postgresql&style=flat"></a>
|
||||
<a href="https://www.postgresql.org"> <img alt="PostgreSQL 11,12,13" src="https://img.shields.io/badge/postgresql-11,_12,_13-green.svg?logo=postgresql&style=flat"></a>
|
||||
</p>
|
||||
|
||||
<h2 align="center">Our Sponsors</h2>
|
||||
@@ -112,30 +112,29 @@ Before you start make sure you have installed:
|
||||
#### Node.js
|
||||
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 | Latest Patch Version | End-of-Life Date | Compatibility |
|
||||
|------------|----------------------|------------------|--------------------|
|
||||
| Node.js 12 | 12.22.0 | April 2022 | ✅ Fully compatible |
|
||||
| Node.js 14 | 14.16.0 | April 2023 | ✅ Fully compatible |
|
||||
| Node.js 15 | 15.13.0 | June 2021 | ✅ Fully compatible |
|
||||
| Version | Latest Version | End-of-Life Date | Compatibility |
|
||||
|------------|----------------|------------------|--------------------|
|
||||
| Node.js 12 | 12.22.1 | April 2022 | ✅ Fully compatible |
|
||||
| Node.js 14 | 14.16.1 | April 2023 | ✅ Fully compatible |
|
||||
| Node.js 15 | 15.14.0 | June 2021 | ✅ Fully compatible |
|
||||
|
||||
#### 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 only test against versions that are officially supported and have not reached their end-of-life date.
|
||||
|
||||
| Version | Latest Patch Version | End-of-Life Date | Compatibility |
|
||||
|-------------|----------------------|------------------|--------------------|
|
||||
| MongoDB 4.0 | 4.0.23 | January 2022 | ✅ Fully compatible |
|
||||
| MongoDB 4.2 | 4.2.13 | TBD | ✅ Fully compatible |
|
||||
| MongoDB 4.4 | 4.4.4 | TBD | ✅ Fully compatible |
|
||||
| Version | Latest Version | End-of-Life Date | Compatibility |
|
||||
|-------------|----------------|------------------|--------------------|
|
||||
| MongoDB 4.0 | 4.0.23 | January 2022 | ✅ Fully compatible |
|
||||
| MongoDB 4.2 | 4.2.13 | TBD | ✅ Fully compatible |
|
||||
| MongoDB 4.4 | 4.4.4 | TBD | ✅ Fully compatible |
|
||||
|
||||
#### PostgreSQL
|
||||
Parse Server is continuously tested with the most recent releases of PostgreSQL and PostGIS to ensure compatibility. We follow the [PostGIS docker tags](https://registry.hub.docker.com/r/postgis/postgis/tags?page=1&ordering=last_updated) 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 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 if a version is older than 3.5 years and a newer version has been available for at least 2.5 years.
|
||||
|
||||
| Version | PostGIS Version | End-of-Life Date | Compatibility |
|
||||
|---------------|-----------------|------------------|--------------------|
|
||||
| Postgres 10.x | 3.0.x, 3.1.x | November 2022 | ✅ Fully compatible |
|
||||
| Postgres 11.x | 3.0.x, 3.1.x | November 2023 | ✅ Fully compatible |
|
||||
| Postgres 12.x | 3.0.x, 3.1.x | November 2024 | ✅ Fully compatible |
|
||||
| Postgres 13.x | 3.0.x, 3.1.x | November 2025 | ✅ Fully compatible |
|
||||
| Version | PostGIS Version | End-of-Life Date | Parse Server Support End | Compatibility |
|
||||
|-------------|-----------------|------------------|--------------------------|--------------------|
|
||||
| Postgres 11 | 3.0, 3.1 | November 2023 | April 2022 | ✅ Fully compatible |
|
||||
| Postgres 12 | 3.1 | November 2024 | April 2023 | ✅ Fully compatible |
|
||||
| Postgres 13 | 3.1 | November 2025 | April 2024 | ✅ Fully compatible |
|
||||
|
||||
### Locally
|
||||
```bash
|
||||
|
||||
Reference in New Issue
Block a user