# Archived patch series Patch sets for upstream versitygw releases this project **no longer builds**. They are kept for reference and reproducibility, not because they are safe to ship. | Patch set | Contents | |-----------|-----------------------------------------------------------| | `v1.8.0/` | `0001-webui-debrand.patch`, `0002-webui-dark-theme.patch` | | `v1.7.0/` | `0001-webui-debrand.patch`, `0002-webui-dark-theme.patch` | | `v1.6.0/` | `0001-webui-debrand.patch`, `0002-webui-dark-theme.patch` | | `v1.5.0/` | `0001-webui-debrand.patch` | ## Why these are not built `v1.10.0` carries upstream CVE fixes that these releases predate. Building them would publish known-vulnerable gateways under this project's release name, so their tags were removed from `ci/support-matrix.yaml`. That matrix is an allowlist — `ci/apply-patches.sh` refuses a tag it does not list, so neither a tag push nor a workflow dispatch can rebuild one by accident. Releases already published for these versions are **not** removed by archiving the patches. Delete them by hand in Gitea if they should no longer be downloadable. ## Rebuilding one anyway If you genuinely need an archived build — reproducing an old report, bisecting a regression — point `PATCH_DIR` at it instead of re-adding it to the matrix: ```bash VGW_TAG=v1.8.0 bash ci/clone-source.sh PATCH_DIR=patches/archive/v1.8.0 VGW_TAG=v1.8.0 bash ci/apply-patches.sh VGW_TAG=v1.8.0 bash ci/build.sh ``` Don't publish the result to a release unless you mean to ship a vulnerable build. ## Un-archiving To return a version to the supported set, `git mv` its directory back to `patches//` and add its row to `ci/support-matrix.yaml`. Rebase the series onto the tag first if upstream has moved — see [../../docs/multi-version-pipeline.md](../../docs/multi-version-pipeline.md).