mirror of
https://github.com/GreptimeTeam/greptimedb.git
synced 2026-08-18 20:18:30 +00:00
discord9
3e63b8abf3
* ci: automate compatibility version window Signed-off-by: discord9 <discord9@163.com> * ci: address compat version window review feedback Address all four review comments on the compat version window automation: - Keep the PR window to the sliding window only (latest patch of the two newest stable minor lines). Exact =vX.Y.Z anchors from case.toml are no longer unioned into from_versions; they are validated by the new --check-anchors mode and exercised by nightly runs via --nightly-window. - Add --published-only: the window is computed over stable git tags that have a published, non-draft GitHub release carrying the sqlness compat artifacts (greptime-linux-amd64 tar.gz and sha256sum), so failed releases cannot land in the window. - Run the updater Python tests plus the window/anchor consistency check in PR and merge-group CI (new compat-updater-check job in integration.yml). - Regenerate tests/compatibility/ci.toml to the current sliding window [v1.0.2, v1.1.4]. Signed-off-by: discord9 <55937128+discord9@users.noreply.github.com> --------- Signed-off-by: discord9 <discord9@163.com> Signed-off-by: discord9 <55937128+discord9@users.noreply.github.com>
13 lines
597 B
TOML
13 lines
597 B
TOML
# Compatibility CI version window.
|
|
#
|
|
# The PR window keeps the latest patch in each of the two most recent stable
|
|
# minor lines whose tags have published release assets. Exact =vX.Y.Z
|
|
# `from_range` anchors in case.toml are validated by --check-anchors and
|
|
# exercised by nightly runs (--nightly-window); they are not retained in the PR
|
|
# window. Run .github/scripts/update-compat-versions.py --update --published-only
|
|
# after release tags land.
|
|
from_versions = ["v1.0.2", "v1.1.4"]
|
|
|
|
# Recent releases that must be able to reopen tables written by the PR build.
|
|
downgrade_to_versions = ["v1.1.4"]
|