Ramsons (R2 2024) Critical Service Patch #9 (Eureka) | GA date: TBD
to be Released at TBD
Approval Log
Tickets list
Required manual migration
Run this SQL, otherwise mod-agreements' migration might fail:
DO $$
DECLARE
record RECORD;
BEGIN
FOR record IN
SELECT schemaname, tablename FROM pg_tables WHERE schemaname LIKE '%_mod_agreements' AND tablename = 'tenant_changelog_lock'
LOOP
EXECUTE format('DELETE FROM %I.%I', record.schemaname, record.tablename);
END LOOP;
DROP SCHEMA IF EXISTS mod_agreements__system CASCADE;
END;
$$ LANGUAGE plpgsql;Modules list
Release tag
Infrastructure
PostgreSQL
Bump the PostgreSQL minor version to fix security issues, for details see https://www.postgresql.org/support/security/ and/or https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-versions.html .
If using 16 upgrade to >= 16.11. FOLIO officially supports 16 only; however, there are no known incompatibilities with 17 and 18.
If using 17 upgrade to >= 17.7.
If using 18 upgrade to >= 18.1.
MinIO
If using MinIO upgrade to latest version to fix security vulnerabilities.
Upgrade to >= RELEASE.2025-10-15T17-29-55Z.
One container download option is https://hub.docker.com/r/cleanstart/minio .
Elasticsearch
If using Elasticseach upgrade to the latest patch version to fix security vulnerabilities, for details see https://www.elastic.co/blog/category/releases
Upgrade to >= 9.2.3, >= 9.1.9, or >= 8.19.9.
OpenSearch
If using OpenSearch upgrade to the latest patch version to fix security vulnerabilities, for details see https://docs.opensearch.org/latest/version-history/
Upgrade to >= 2.19.4, or >=3.3.2.
folio-kong
If using folio-kong upgrade folio-kong to latest version to fix security vulnerabilities: https://github.com/folio-org/folio-kong/releases
Upgrade to >= 3.9.1.
folio-keycloak
If using folio-keycloak upgrade folio-keycloak to latest version to fix security vulnerabilities: https://github.com/folio-org/folio-keycloak/releases
Upgrade to >= 26.4.3.