Page Properties | ||||||
---|---|---|---|---|---|---|
|
...
- Jest
- should be 29 or greater
- RTL
- should be 14 greater
Post Build Integration Testing
...
- Java 21 / JDK 21
- Keycloak 25.0.0 release notes: "OpenJDK 17 support is deprecated in Keycloak, and will be removed in a following release in favor of OpenJDK 21."
- Other software libraries used by FOLIO will also drop 17 support soon.
- Java 21 more efficiently uses CPU resources (virtual threads, improved garbage collection, etc.) saving costs for implementers and devops.
- New language features improve developer satisfaction and code quality/correctness.
- Grails modules use at least Java 17
- Groovy (version determined by the version of Grails, below)
- OpenAPI (OAS) 3
- Go 1.25 or greater (expected release in ~August 2025)
- See https://go.dev/doc/devel/release#policy: Go 1.24 support period is 2025-02 until ~ 2026-02, Go 1.25 support period is ~ 2025-08 until ~ 2026-08
Build Tools
Policy: One of Specified versions
...
- Postgresql 16
- OpenSearch 3 and Elasticsearch 8
- OpenSearch release schedule and maintenance policy
- Elasticsearch support policy, EOL dates, release history
- MSK/Kafka
- Kafka 3.8 - See https://endoflife.date/apache-kafka and https://github.com/apache/kafka/branches; an open source minor version is supported for ~ 12 months; we expect 4.0 release ~ Feb 2025 and 4.1 release ~ July 2025
- MSK - See https://docs.aws.amazon.com/msk/latest/developerguide/supported-kafka-versions.html (we expect 3.8 to be supported by MSK ~Oct 2025)
- S3/MInIO - Current version of MinIO compatible with S3
- FOLIO Kong 3.7.* (Built on Kong v)
- Latest version
- Versioning approach for folio-kong and folio-keycloak
- This may or may not be helpful, but here are the support policies for Kong Enterprise: https://docs.konghq.com/gateway/latest/support-policy/
- Kong Open Source Software (OSS) = Community Edition essentially only supports the most recent release, which is 3.9 as of . Releases (Enterprise Support Policy) typically happen every 3-4 months.
- Rough prediction based on the 3-4 mo. release cadence:
- Dec `24 - 3.9 (current latest)
- Mar `25 - 3.10
- Jun `25 - 3.11
- Sept `25 - 3.12
- Dec `25 - 3.13
- FOLIO Keycloak 26.1.* (Built on Keycloak v)
- Latest version
- Versioning approach for folio-kong and folio-keycloak
- Only the latest major version gets active development and security fixes. Depending on the severity of a vulnerability, the issue may be fixed in the current release or, for lower severity vulnerabilities or hardening, in the following release.
- See https://github.com/keycloak/keycloak/security/policy#supported-versions
... after Keycloak 26.0 is released there will be some changes to how Keycloak is being released:
Keycloak server will have 4 minor releases every year, and a major release every 2-3 years
Keycloak client libraries will be released separately. The latest client library release will support all currently supported Keycloak server releases
- Rough prediction based on the above:
- Jan `25 - 26.1
- May `25 - 26.2
- Aug `25 - 26.3
- Nov `25 - 26.4
...
Fast moving infrastructure
Policy: System operators are highly encouraged to update to the latest versions of these components as they are released.
- FOLIO Kong 3.7.* (Built on Kong v)
- Latest version
- Versioning approach for folio-kong and folio-keycloak
- This may or may not be helpful, but here are the support policies for Kong Enterprise: https://docs.konghq.com/gateway/latest/support-policy/
- Kong Open Source Software (OSS) = Community Edition essentially only supports the most recent release, which is 3.9 as of . Releases (Enterprise Support Policy) typically happen every 3-4 months.
- Rough prediction based on the 3-4 mo. release cadence:
- Dec `24 - 3.9 (current latest)
- Mar `25 - 3.10
- Jun `25 - 3.11
- Sept `25 - 3.12
- Dec `25 - 3.13
- FOLIO Keycloak 26.1.* (Built on Keycloak v)
- Latest version
- Versioning approach for folio-kong and folio-keycloak
- Only the latest major version gets active development and security fixes. Depending on the severity of a vulnerability, the issue may be fixed in the current release or, for lower severity vulnerabilities or hardening, in the following release.
- See https://github.com/keycloak/keycloak/security/policy#supported-versions
... after Keycloak 26.0 is released there will be some changes to how Keycloak is being released:
Keycloak server will have 4 minor releases every year, and a major release every 2-3 years
Keycloak client libraries will be released separately. The latest client library release will support all currently supported Keycloak server releases
- Rough prediction based on the above:
- Jan `25 - 26.1
- May `25 - 26.2
- Aug `25 - 26.3
- Nov `25 - 26.4
...
Technology versions must support the full Sunflower support period that ends around Q1 2026: Sunflower will be released in Q2 2025 and will be supported until Umbrellaleaf (R1 2026) gets released around Q1 2026 (based upon assumption that future releases will follow a similar cadence to previous releases), see FOLIO support policy.
Release name | Release Date* | End of Support* |
---|---|---|
Sunflower | Q2 2025 | Q2 2026 |
Trillium | Q4 2025 | Q4 2026 |
Umbrellaleaf | Q2 2026 | Q2 2027 |
* Current best guess