generated: '2026-10-09'
method: searched
source:
- https://dev.folio.org/guidelines/naming-conventions/
- https://dev.folio.org/guidelines/release-procedures/
- https://folio-org.atlassian.net/wiki/spaces/REL/overview
versioning:
  scheme: semantic versioning for modules; major.minor for interfaces; named platform releases
  module_versioning: The version number of a module uses semantic versioning.
  interface_versioning: The version number of an interface uses the first two portions of semantic versioning. There does
    not need to be any correlation between the module version and the version of the interfaces it implements.
  release_cadence: FOLIO follows a regular release cycle, currently with two releases each year.
  bugfix_branches: We use the naming scheme b followed by the major and minor versions, for example b2.17 which will include
    all bug fixes for version 2.17 (so for v2.17.1 and v2.17.2).
deprecation:
  policy: null
  sunset_headers: false
  note: No published API deprecation policy or Sunset/Deprecation header usage was found on the pages read.
  deprecated_operations:
  - operationId: getColumnValues
    spec: openapi/folio-folio-query-tool-metadata-querytool-openapi.yml
  derived_from: openapi/ (operations marked deprecated true; further deprecated flags in the specs are on schema properties)
status_page: null
sla: null
note: FOLIO is self-hosted; there is no central production API, so no project status page or SLA applies. Each deployment's
  operator is responsible for availability.