release.yaml

# CloudFile release manifest.
#
# Upstream 14.0 CE is not released: haiwen/seafile-server has no 14.0 branch and
# 14.0 carries only "-pro" tags, no "-server" (CE) tags. CloudFile therefore
# anchors every component to an explicit commit SHA rather than to a tag.
#
# The build script (build/cloudfile_14.0/cloudfile-build.sh) reads this file and
# checks out exactly these refs. Bump the SHAs here, never in the build script.

product: 14.0.0-cf.0
image: cloudfile/cloudfile:14.0.0-cf.0
build_base_image: cloudfile-build-base:ce14-v2
ubuntu_base_image: ubuntu:24.04

# Filled in at release time with the CloudFile commit each image was built from.
server_commit: ""
hub_commit: ""
docker_commit: ""

# CloudFile forks.
#
# `dev` is the extension baseline: seams, build and deploy machinery, and no
# capabilities. A capability build points these at its own long-lived branch,
# e.g. ref: feature/dir-acl on both. CF_SERVER_REF / CF_HUB_REF override them
# without editing this file.
forks:
  cloudfile_server:
    url: https://github.com/eaopen/cloudfile-server.git
    ref: dev
  cloudfile_hub:
    url: https://github.com/eaopen/cloudfile-hub.git
    ref: dev

# Not forked - pinned to the upstream commits the fork baseline was cut from.
upstream:
  seafile_server: 0e83ffdd16ce85e35d435d3b8f899a82b6b780d0
  seahub: da3334e1d17caddf16120c60442307eb5d3946da
  seafile_docker: 9a925bcc19eba95582d90ec8dd21030e0b4717e6
  seafobj: 794428d5f455338f2f2f472c1f0ee2eebf623103
  seafdav: 1ce0b05ea7d04495a1ca9121fc58c30d63b71e36
  seafevents: d07b9e885de866454b5c42bed5834ca82959f303
  libsearpc: 23d5df62815fb3b7825bf4e1a28b29af701e8cb2
  libevhtp: 291aedae9dda722976cf0dcece66105c93758729

# Bump when cf_* tables change shape; the upgrade path keys off this.
# 1 -> 2 (2026-08-17): added cf_dir_admin (directory-level delegated manage).
# Additive, IF NOT EXISTS, auto-applied by the bootstrap on every start -- no
# manual migration step.
database_schema: 2
# Bump when cloudfile_ext.registry hook signatures change.
extension_api: 1