57_WolveandClaude Opus 5
4852777c57
Upstream released v1.11.0 (e42ae7a, 2026-11-06): 42 commits, mostly
fixes, plus two WebUI features that add ~415 lines to explorer.html
(on-demand bucket size calculation, restore archived objects).
The series needed no content changes — the regenerated patches differ
from the v1.10.0 ones only in their `index <blob>..<blob>` lines, since
the de-brand edits sit above the regions upstream touched. Regenerating
them is still worthwhile: the v1.10.0 patches' pre-image blobs do not
exist in a v1.11.0 clone, so `git am --3way` could not use its 3-way
fallback and was silently applying them directly.
Verified before committing:
- round-trips from a clean clone to tree 8d509fe
- residual branding identical to the patched v1.10.0 tree (23
occurrences, same per-file spread, no regressions)
- all 5 light-mode Tailwind classes in the new explorer markup are
overridden in theme.css
- series touches only webui/; file count 1049 -> 1051
- goreleaser builds all 8 targets plus deb/rpm
- matrix accepts v1.11.0, refuses v1.10.0, PATCH_DIR still rebuilds
the archived series
v1.10.0 moves to patches/archive/ as *superseded*, not vulnerable: it is
the release carrying upstream's CVE-2026-111943 notice, and that fix
comes from the Go toolchain (>= 1.26.10 / 1.27.3) rather than from the
tag. The archive README and the top-level README now say so, instead of
implying every archived series predates a security fix.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
24 lines
987 B
YAML
24 lines
987 B
YAML
# s3-gateway build support matrix — single source of truth for CI.
|
|
#
|
|
# This is an ALLOWLIST. ci/apply-patches.sh refuses to build any tag
|
|
# that is not listed here, so a stale or vulnerable upstream release
|
|
# cannot be published by a stray tag push or a mistyped dispatch.
|
|
#
|
|
# Each entry maps an upstream versitygw release tag to the patch set
|
|
# (a directory under patches/) applied on top of that tag before
|
|
# building. Add a row when upstream cuts a release you want a
|
|
# de-branded build of; remove one to stop building it. See
|
|
# docs/multi-version-pipeline.md for the patch-refresh workflow.
|
|
#
|
|
# The highest-version entry is treated as "latest".
|
|
#
|
|
# Superseded series are kept under patches/archive/<tag>/ rather than
|
|
# deleted — see that directory's README to rebuild one deliberately.
|
|
#
|
|
# tag upstream versitygw git tag (github.com/versity/versitygw)
|
|
# patches directory under patches/ to apply (defaults to `tag`)
|
|
|
|
versitygw:
|
|
- tag: v1.11.0
|
|
patches: v1.11.0
|