...

Reasoning: Adopting new versions of these technologies may have substantial impact on shared community tooling or hosting providers

Chosen Technologies:

• Node 2220
• Yarn 1
• TBD: There is an open spike (STRIPES-907) from stripes-force to investigate alternate build strategies.

First Party Libraries / Frameworks

...

Chosen Technologies:

• Stripes 910.20.0 or greater

Shared Third Party Libraries / Frameworks

...

Chosen Technologies:

• React 18.2 or 19.0

During Build Automated Testing

...

• Jest
  • should be 29 or greater
• RTL
  • should be 14 greater

Post Build Integration Testing

...

Reasoning: Adopting new versions of these technologies may have substantial impact on shared community tooling or hosting providers

Chosen Technologies:

• Java 17 21 /  JDK 17JDK 21
• Groovy (version determined by the version of Grails, below)
• OpenAPI (OAS) 3
  • see https://dev.folio.org/start/primer-oas/

...

Reasoning: The FOLIO community has previously adopted the policy that first party technologies must be synchronised across all modules within the system for easier support

Notes:

• These versions are often only decided upon in the latter states of the flower release process and may be subject to change even after this document is accepted.
• A first party library/framework needs to support only one of the versions allowed in the "Third Party Libraries / Frameworks" list.

Chosen Technologies:

• folio-spring-base 8.1 or greater
• folio-vertx-lib 3.2 or greater
• raml-module-builder 35
  • deprecated. Only existing FOLIO modules may continue to use raml-module-builder
• edge-common 4.5.2 or greater
• edge-common-spring 2.3.2 or greater
• https://github.com/folio-org/folio-s3-client 2.1.1 or greater

Third Party Libraries / Frameworks

...

Reasoning: These technologies are only used within a module. It is reasonable for the versions to vary between modules as the choice does not affect other modules or centralised centralized community tooling

Notes: A first party library/framework may support only one of these versions.

Chosen Technologies:

• Spring Boot
  • 3.3 4 or later recommended (OSS support until 2025-0511)
• Spring Framework
  • 6.1 2 or later recommended (OSS support until 20252026-08-31)
• Grails
• Eclipse Vert.x 4
  • See https://projects.eclipse.org/projects/rt.vertx and https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/760
    
• Lombok
• AWS SDK for Java
  • version 2 (version 1 will reach end-of-support on December 31, 2025)
• MinIO Client library 8.5 or higher recommended

During Build Automated Testing

...

Reasoning: These technologies are only used for automated testing within the module. It is reasonable for the versions to vary between modules as the choice does not affect other modules or centralised centralized community tooling

Chosen Technologies:

...

• Postgresql 16
• OpenSearch 2 and Elasticsearch 8
  • OpenSearch maintenance policy
  • Elasticsearch support policy, EOL dates, release history
• MSK/Kafka - 3.5.1 
• S3/MInIO - Current version of MinIO compatible with S3
  

...

Policies

Policies should use the language described in RFC-2119

...

Technology versions must support the full Ramsons Sunflower support period that ends around April 2025Q1 2026: Ramsons Sunflower will be released in August 2024 Q2 2025 and will be supported until Trillium Umbrellaleaf (R1 20252026) gets released around April 2025 Q1 2026 (based upon assumption that future releases will follow a similar cadence to previous releases), see FOLIO support policy.

^* Current best guess