Refresh HiveGrid Cloud reference snapshot

This commit is contained in:
david committed 2026-08-03 15:31:14 +02:00
1 parent 5e99e14772
commit 7f88026f79
5955 files changed
+1177325 -188362

No files matched your search

@@ -6,6 +6,7 @@
| --- | --- |
| Upstream repo | <https://github.com/getsentry/self-hosted> |
| Pinned git tag | **`25.12.1`** |
| Pinned commit | **`5c9794c9b1fda551f38515f85d56ec298371d060`** |
| Release line | `v25.x` (LTS-ish; we treat the v25.x line as our long-term track until v26.x is qualified) |
| Why not `25.12.0` | `25.12.0` shipped a known migration bug in the `snuba-api` migration step that aborts the installer mid-way; `25.12.1` is the hotfix. |
| Why not `26.x` | v26.x is the current major and introduces breaking schema changes (Snuba consumers + ClickHouse-table renames). We intentionally trail one major behind to land changes after they have been hot-fixed in the wild. |
@@ -37,21 +38,22 @@ at deploy time inside our own wrapper. Our repository only contains the
- `install.sh` — wrapper that clones upstream + applies overlays + invokes
the upstream installer
## Clone strategy (what `install.sh` does)
## Fetch strategy (what `install.sh` does)
The wrapper performs the equivalent of:
The tag is release metadata only. The wrapper executes the immutable commit
that the tag resolved to when this pin was reviewed:
```bash
# Clone exactly the pinned tag into infra/sentry/upstream/self-hosted/,
# shallow + single-branch to keep the working tree lean.
git clone \
--branch 25.12.1 \
--depth 1 \
--single-branch \
https://github.com/getsentry/self-hosted.git \
infra/sentry/upstream/self-hosted
git -C infra/sentry/upstream/self-hosted init
git -C infra/sentry/upstream/self-hosted remote add origin https://github.com/getsentry/self-hosted.git
git -C infra/sentry/upstream/self-hosted fetch --depth 1 origin 5c9794c9b1fda551f38515f85d56ec298371d060
git -C infra/sentry/upstream/self-hosted checkout --detach 5c9794c9b1fda551f38515f85d56ec298371d060
```
The installer then compares `rev-parse HEAD` with the pinned commit and aborts
on any mismatch. Moving or replacing the upstream tag therefore cannot change
the executed installer.
After cloning, the wrapper:
1. Copies `infra/sentry/docker-compose.override.yml` →
@@ -74,7 +76,8 @@ repo for a fresh checkout but stays empty until the first `install.sh` run.
To upgrade to a newer `25.x.y` patch:
1. Update the tag in this file (`UPSTREAM.md`) and in `install.sh`.
1. Resolve and review the new tag, then update both tag and immutable commit in
this file (`UPSTREAM.md`) and in `install.sh`.
2. Read upstream release notes for any `sentry.conf.py` migrations and
sync our overlay if upstream renamed/removed any setting we override.
3. On staging, run `./install.sh` again. The upstream installer is