docs: finalize beta2 release evidence

Signed-off-by: discord9 <discord9@163.com>
2026-10-15 08:22:38 +00:00 · 2026-08-21 22:57:15 +08:00
parent 69a9448aae
commit 0f865d6ef8
3 changed files with 6 additions and 6 deletions
@@ -6,7 +6,7 @@
 - Aggregate branch: `work/release-v1.2-beta2-complete`
 - Aggregate head: `cb52adcbf798d3d2f009874f46dc5d476073bd8c`
 - Aggregate commits: 49 (the prior 48-commit aggregate history plus the #8752 secure_fs test-portability follow-up)
- CI evidence: Historical [GitHub Actions run 32341712112](https://github.com/GreptimeTeam/greptimedb/actions/runs/32341712112), whose actual head SHA was `b5c38fbfc15053f42d4c1d843204bbdd52cb4a00`, failed on the superseded-base aggregate: Clippy, Check Unused Dependencies, and Check (ubuntu-latest) failed; SQLness, Compatibility Test, binary builds, Rustfmt, license, and fuzz passed; `test` was skipped downstream because Clippy and Check Unused Dependencies failed, while `coverage` was skipped independently because this was a `workflow_dispatch` run and coverage runs only for `merge_group`. The later [Release run 32462587383](https://github.com/GreptimeTeam/greptimedb/actions/runs/32462587383) was triggered at the pre-#8751 head `81fd630955f16b9c45811539aa8434b47d5a875b`: its Windows job `96713326607` failed in the composite Windows-artifact step, while the overall run was subsequently cancelled and dependent jobs were cancelled. The refreshed Release run [32466550985](https://github.com/GreptimeTeam/greptimedb/actions/runs/32466550985) Windows job `96725255397` also failed. These Windows results are evidence of job outcomes, not a diagnosis and not final CI success for the refreshed head. Final-head tag-push [Release run 32470573285](https://github.com/GreptimeTeam/greptimedb/actions/runs/32470573285) has started at `cb52adcbf798d3d2f009874f46dc5d476073bd8c`; no final CI result is claimed yet for `2f5e97850e55d86c0ed9eff1719994c88b4450a0..cb52adcbf798d3d2f009874f46dc5d476073bd8c`.
+- CI evidence: Historical [GitHub Actions run 32341712112](https://github.com/GreptimeTeam/greptimedb/actions/runs/32341712112), whose actual head SHA was `b5c38fbfc15053f42d4c1d843204bbdd52cb4a00`, failed on the superseded-base aggregate: Clippy, Check Unused Dependencies, and Check (ubuntu-latest) failed; SQLness, Compatibility Test, binary builds, Rustfmt, license, and fuzz passed; `test` was skipped downstream because Clippy and Check Unused Dependencies failed, while `coverage` was skipped independently because this was a `workflow_dispatch` run and coverage runs only for `merge_group`. The later [Release run 32462587383](https://github.com/GreptimeTeam/greptimedb/actions/runs/32462587383) was triggered at the pre-#8751 head `81fd630955f16b9c45811539aa8434b47d5a875b`: its Windows job `96713326607` failed in the composite Windows-artifact step, while the overall run was subsequently cancelled and dependent jobs were cancelled. The refreshed Release run [32466550985](https://github.com/GreptimeTeam/greptimedb/actions/runs/32466550985) Windows job `96725255397` also failed. These Windows results are evidence of job outcomes, not a diagnosis and not final CI success for the refreshed head. Final-head tag-push [Release run 32470573285](https://github.com/GreptimeTeam/greptimedb/actions/runs/32470573285) at `cb52adcbf798d3d2f009874f46dc5d476073bd8c` completed all platform artifacts and Compatibility Test successfully, then was cancelled because the query regression was queued on unavailable `perf-regression-8-cores`. Same-tag [workflow_dispatch recovery run 32487995883](https://github.com/GreptimeTeam/greptimedb/actions/runs/32487995883) completed successfully with `release_validation=skip-all`: query regression and Compatibility Test were skipped, so neither skipped validation is claimed as passed; platform artifacts, DockerHub images, and GitHub release publication succeeded. GitHub release `v1.2.0-beta.2` is `draft=false`, `prerelease=true`, published at `2026-08-21T14:51:51Z`, with 14 assets.
 - `release/v1.2` was fast-forwarded to the aggregate head `cb52adcbf798d3d2f009874f46dc5d476073bd8c`; the range remains linear with zero merge commits.

 ## How to read the artifacts
@@ -48,7 +48,7 @@ The upstream PR has two hunks: a production cleanup in `src/common/meta/src/ddl/
 - After #8751: Main recorded a 20/20 no-retry pass, log SHA `fa9ae951fa78dce66c7b0aedc81cd172c9fc898445712162c616c99aeb7000d8`.
 - After #8751: common-meta recorded a 546/546 no-retry pass, log SHA `84b54cdff1767a2c0e0683e59a955472eacabc769871c5d893940f07d932a79a`.

-These are local before/after verification records; they do not overstate the cancelled Release run as final CI.
+These are local before/after verification records; final release evidence is recorded in the CI evidence above.

 ## Accepted breaking-format exception

@@ -66,4 +66,4 @@ PR #8902 is carried by pre-version commit `40e02ff6b62ad3445f7035e437bd9e322c8af

 Upstream PR [#8752](https://github.com/GreptimeTeam/greptimedb/pull/8752), merge `4e43c279ff29e9071394f85b90b874906115d29f`, is appended as a test-only dependency-closure/follow-up relationship for the #8735/#8708 `secure_fs` behavior chain. The target parent lacked the #8735 context, so this carrier is adapted to the beta2 parent; the resulting test body matches final main. Carrier `cb52adcbf798d3d2f009874f46dc5d476073bd8c` changes only `src/object-store/src/secure_fs.rs`, preserving the portable call/path checks while gating the strong `is_none()` assertion to non-Windows. See [`range-diffs/pr-8752.txt`](range-diffs/pr-8752.txt).

-Oracle review: **APPROVE**. Focused Main verification passed 20/20 without retry, log SHA `fc831f2b2d51c79e8b1fbc6267e8fe8bac90d06c746e1136067e9bcbcbec40df`; fixer focused verification and full object-store verification each passed 20/20 without retry. No native Windows post-fix run has been performed yet, and no final CI success is claimed. Release run [32466550985](https://github.com/GreptimeTeam/greptimedb/actions/runs/32466550985) Windows job `96725255397` failed; this is recorded as a failure only and is not treated as final refreshed-head CI success.
+Oracle review: **APPROVE**. Focused Main verification passed 20/20 without retry, log SHA `fc831f2b2d51c79e8b1fbc6267e8fe8bac90d06c746e1136067e9bcbcbec40df`; fixer focused verification and full object-store verification each passed 20/20 without retry. Earlier Release run [32466550985](https://github.com/GreptimeTeam/greptimedb/actions/runs/32466550985) Windows job `96725255397` failed; final release evidence is recorded in the CI evidence above.
@@ -11,9 +11,9 @@ not edited.

 ## Canonical CI status

-The recorded historical [GitHub Actions run 32341712112](https://github.com/GreptimeTeam/greptimedb/actions/runs/32341712112), whose actual head SHA was `b5c38fbfc15053f42d4c1d843204bbdd52cb4a00`, failed on the superseded-base aggregate: Clippy, Check Unused Dependencies, and Check (ubuntu-latest) failed; SQLness, Compatibility Test, binary builds, Rustfmt, license, and fuzz passed; `test` was skipped downstream because Clippy and Check Unused Dependencies failed, while `coverage` was skipped independently because this was a `workflow_dispatch` run and coverage runs only for `merge_group`. The later [Release run 32462587383](https://github.com/GreptimeTeam/greptimedb/actions/runs/32462587383) ran at pre-#8751 head `81fd630955f16b9c45811539aa8434b47d5a875b`; Windows job `96713326607` failed in the composite Windows-artifact step, and the overall run was subsequently cancelled with dependent jobs cancelled. The refreshed [Release run 32466550985](https://github.com/GreptimeTeam/greptimedb/actions/runs/32466550985) Windows job `96725255397` also failed. These are Windows job outcomes, not root-cause attribution and not final CI success for the refreshed head. Final-head tag-push [Release run 32470573285](https://github.com/GreptimeTeam/greptimedb/actions/runs/32470573285) has started at `cb52adcbf798d3d2f009874f46dc5d476073bd8c`; no final result is claimed yet.
+The recorded historical [GitHub Actions run 32341712112](https://github.com/GreptimeTeam/greptimedb/actions/runs/32341712112), whose actual head SHA was `b5c38fbfc15053f42d4c1d843204bbdd52cb4a00`, failed on the superseded-base aggregate: Clippy, Check Unused Dependencies, and Check (ubuntu-latest) failed; SQLness, Compatibility Test, binary builds, Rustfmt, license, and fuzz passed; `test` was skipped downstream because Clippy and Check Unused Dependencies failed, while `coverage` was skipped independently because this was a `workflow_dispatch` run and coverage runs only for `merge_group`. The later [Release run 32462587383](https://github.com/GreptimeTeam/greptimedb/actions/runs/32462587383) ran at pre-#8751 head `81fd630955f16b9c45811539aa8434b47d5a875b`; Windows job `96713326607` failed in the composite Windows-artifact step, and the overall run was subsequently cancelled with dependent jobs cancelled. The refreshed [Release run 32466550985](https://github.com/GreptimeTeam/greptimedb/actions/runs/32466550985) Windows job `96725255397` also failed. These are Windows job outcomes, not root-cause attribution and not final CI success for the refreshed head. Final-head tag-push [Release run 32470573285](https://github.com/GreptimeTeam/greptimedb/actions/runs/32470573285) at `cb52adcbf798d3d2f009874f46dc5d476073bd8c` completed all platform artifacts and Compatibility Test successfully, then was cancelled because the query regression was queued on unavailable `perf-regression-8-cores`. Same-tag [workflow_dispatch recovery run 32487995883](https://github.com/GreptimeTeam/greptimedb/actions/runs/32487995883) completed successfully with `release_validation=skip-all`: query regression and Compatibility Test were skipped, so neither skipped validation is claimed as passed; platform artifacts, DockerHub images, and GitHub release publication succeeded. GitHub release `v1.2.0-beta.2` is `draft=false`, `prerelease=true`, published at `2026-08-21T14:51:51Z`, with 14 assets.

-Recorded local before/after verification is: before #8751, Main 4/4 failed; after #8751, Main 20/20 passed with no retry (log SHA `fa9ae951fa78dce66c7b0aedc81cd172c9fc898445712162c616c99aeb7000d8`), and common-meta 546/546 passed with no retry (log SHA `84b54cdff1767a2c0e0683e59a955472eacabc769871c5d893940f07d932a79a`). For #8752, focused Main passed 20/20 without retry (log SHA `fc831f2b2d51c79e8b1fbc6267e8fe8bac90d06c746e1136067e9bcbcbec40df`); fixer focused and full object-store verification each recorded 20/20 without retry. No final CI result is claimed for the refreshed range `2f5e97850e55d86c0ed9eff1719994c88b4450a0..cb52adcbf798d3d2f009874f46dc5d476073bd8c`; these are recorded local verification results only.
+Recorded local before/after verification is: before #8751, Main 4/4 failed; after #8751, Main 20/20 passed with no retry (log SHA `fa9ae951fa78dce66c7b0aedc81cd172c9fc898445712162c616c99aeb7000d8`), and common-meta 546/546 passed with no retry (log SHA `84b54cdff1767a2c0e0683e59a955472eacabc769871c5d893940f07d932a79a`). For #8752, focused Main passed 20/20 without retry (log SHA `fc831f2b2d51c79e8b1fbc6267e8fe8bac90d06c746e1136067e9bcbcbec40df`); fixer focused and full object-store verification each recorded 20/20 without retry. These remain recorded local verification results; the recovery run skipped query regression and Compatibility Test rather than passing them.

 ## 1. BLOCKING / compatibility decisions

@@ -171,4 +171,4 @@ The final review records 36 public Issue-requested PR relationships: the origina
 - Upstream merge: `4e43c279ff29e9071394f85b90b874906115d29f`; aggregate carrier: `cb52adcbf798d3d2f009874f46dc5d476073bd8c`.
 - This is the #8735/#8708 secure_fs behavior follow-up. The target parent lacks #8735 context, so the carrier is adapted to the release parent; the resulting `test_lister_skips_entry_removed_during_iteration` body matches final main and keeps the portable path assertion while gating `is_none()` to non-Windows.
 - It is test-only and adds the 40th provenance relationship. Raw evidence: [`range-diffs/pr-8752.txt`](range-diffs/pr-8752.txt).
- Oracle: APPROVE. Focused Main 20/20 no-retry log SHA `fc831f2b2d51c79e8b1fbc6267e8fe8bac90d06c746e1136067e9bcbcbec40df`; fixer focused and full object-store 20/20 no-retry passes. No native Windows post-fix run yet; no final CI success claimed. Release run `32466550985`, Windows job `96725255397`, failed.
+- Oracle: APPROVE. Focused Main 20/20 no-retry log SHA `fc831f2b2d51c79e8b1fbc6267e8fe8bac90d06c746e1136067e9bcbcbec40df`; fixer focused and full object-store verification each passed 20/20 without retry. Final-head tag-push [Release run 32470573285](https://github.com/GreptimeTeam/greptimedb/actions/runs/32470573285) at `cb52adcbf798d3d2f009874f46dc5d476073bd8c` completed all platform artifacts and Compatibility Test successfully, then was cancelled because query regression was queued on unavailable `perf-regression-8-cores`. Same-tag [workflow_dispatch recovery run 32487995883](https://github.com/GreptimeTeam/greptimedb/actions/runs/32487995883) completed successfully with `release_validation=skip-all`; query regression and Compatibility Test were skipped, not passed, while platform artifacts, DockerHub images, and GitHub release publication succeeded. Release `v1.2.0-beta.2` is `draft=false`, `prerelease=true`, published at `2026-08-21T14:51:51Z`, with 14 assets. Earlier Release run `32466550985`, Windows job `96725255397`, failed.