ci: restore the release pipeline work (#391, #387, #393, #394) - #397
Merged
Conversation
Re-applies the exact tree validated at 8b97994, which passed 22 checks on the head of #394. Verified byte-identical: `git diff 8b97994` is empty. What this contains, per reverted PR: - #391 scripts/check_ci_gate_complete.py — the `CI Green` aggregate. - #387 .github/actions/test-suite/action.yml — one test suite shared by ci.yml and release.yml instead of two drifting copies. - #393 scripts/check_version_surfaces.py — one gate over all 14 version sites, pyproject.toml as the single canonical source. - #394 the tag becomes an output of a green tree rather than a hand-pushed input. No branch-protection change is required or requested. All eleven required contexts keep their exact names — Lint, Type Check, Build Package, Docker Smoke, Test (Python 3.10/3.11/3.12/3.13), Test (SQLite backend), Test (Windows, SQLite backend) — this only adds jobs alongside them. `CI Green` is not proposed as a required context; it gates the tag, which needs no protection change to be enforced.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Réapplique l'arbre exact validé en
8b979947, qui avait passé 22 checks sur la tête de #394. Vérifié :git diff 8b979947est vide, l'arbre est identique au bit près.Ce que ça contient
scripts/check_ci_gate_complete.py— l'agrégatCI Green.github/actions/test-suite/action.yml— une suite de tests partagée parci.ymletrelease.ymlau lieu de deux copies qui divergentscripts/check_version_surfaces.py— un seul gate sur les 14 sites de version,pyproject.tomlcomme source canonique uniqueAucun changement de protection de branche
Les onze contextes requis gardent leurs noms exacts —
Lint,Type Check,Build Package,Docker Smoke (bare-container DB-less contract),Test (Python 3.10/3.11/3.12/3.13),Test (SQLite backend),Test (Windows, SQLite backend). Cette PR n'en renomme aucun et n'en supprime aucun : elle ajoute trois jobs à côté.CI Greenn'est pas proposé comme contexte requis. Son rôle ici est de conditionner la pose du tag, ce qui est appliqué par le workflow lui-même et n'exige aucune modification de la protection.Historique
Le premier passage de ce travail a été reverté de
main(2d73e95d) à la demande du mainteneur. Le code n'était pas en cause : la PR #395 était restée bloquée parce que son trigger CodeQL avait été perdu par un rebase forcé suivi d'un retarget et d'un close/reopen. Cette PR est créée depuismaincourant et ne sera ni retargetée ni rebasée de force.