Repository navigation
Expand file tree
/
Copy pathrelease.yaml
More file actions
73 lines (68 loc) · 3.41 KB
/
Copy pathrelease.yaml
File metadata and controls
73 lines (68 loc) · 3.41 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
# Current single CloudFile build entry: full Server/Hub dev trees.
# CloudFile release manifest.
#
# Upstream CE 14 is released now: haiwen/seafile-server and haiwen/seahub both
# carry a v14.0.8-server tag, and upstream ships the CE 14 image recipe in
# image/seafile_14.0/. Neither repo has a 14.0 branch, so CE 14 still tracks
# master, and the components CloudFile does not fork stay pinned to explicit
# commit SHAs -- they are versioned independently of that release, so there is
# no CE tag to point at.
#
# The build script (build/cloudfile_14.0/cloudfile-build.sh) reads this file and
# resolves these branch refs once into build-receipt.json before any build.
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
# CloudFile forks.
#
# dev is the sole active V2 line. Explicit PR refs may be selected for tests;
# the resulting immutable source lock is generated, never maintained here.
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
cloudfile_docker:
url: https://github.com/eaopen/cloudfile-docker.git
ref: dev
# Not forked. These are the upstream commits each fork is currently synced to.
# tools/gates/check-upstream-patches.sh uses them as its diff base in CI, where the
# clone is too shallow to compute a merge base and the comparison is a two-point
# diff -- so an anchor left behind makes CI report the un-merged upstream commits
# as CloudFile modifications. Bump them in the same change that merges upstream.
# Build inputs are forks.* and the seafobj/seafdav/seafevents/libsearpc/libevhtp
# entries below; these three are only the CI comparison base.
upstream:
seafile_server: d9ed57e1d2ac9888a7c04f15158f2403a9411ce3
seahub: 6d2452ba95f52fb99388bae22ba957f1ff764b16
seafile_docker: 566b7e5e0911fb84c8b1f843efbaf8b928c6de7d
seafobj: 794428d5f455338f2f2f472c1f0ee2eebf623103
seafdav: 1ce0b05ea7d04495a1ca9121fc58c30d63b71e36
seafevents: d07b9e885de866454b5c42bed5834ca82959f303
libsearpc: 23d5df62815fb3b7825bf4e1a28b29af701e8cb2
libevhtp: 91071e2f20749cd469b87ac2ef1c158dc2a6806f # annotated v1.1.6 tag object 291aedae peeled to this source commit
# The upstream CE 14 release CloudFile claims compatibility with. CloudFile
# tracks upstream/master (syncs stay small) but must never fall behind the CE
# release, so each entry below is the *source* commit of that release and
# tools/gates/check-ce-anchor.sh asserts the fork's dev contains it.
#
# seafile-server's v14.0.8-server tag sits on that source commit. seahub's tag
# sits on a "[dist][CI SKIP] ... CI build" artifact commit instead of its source,
# so the recorded SHA is the source commit the artifact was built from (the tag's
# parent). Recording the tag's own commit for seahub would make the assertion
# permanently false.
#
# Bump both when upstream tags a newer v14.0.N-server.
ce_anchor:
version: v14.0.8-server
seafile_server: 17e4b875c2118233830316392ed76a736b374c69
seahub: 3c408439bfca54dbad61e2f6cdb706d2dcdf9f7a
# Historical manifest counter retained for receipt compatibility only.
# It is not a schema owner and must not trigger bootstrap DDL. V2 uses the
# fixed, manually executed SQL package in database/v2/20261021-four-table-baseline/.
database_schema: 3
# Bump when cloudfile_ext.registry hook signatures change.
extension_api: 1