Skip to content

v1.12.0

Choose a tag to compare

@github-actions github-actions released this 25 Oct 09:17
· 54 commits to main since this release
c0020e5

Upgrade notes

  • make verify now runs the live integration lane (#1018) — it runs make check, the
    complete offline make test and then the run-owned make integration lane (default
    INTEGRATION_DRIVER=pycubrid), so it needs Docker and takes as long as the live suite. It
    fails when CUBRID never becomes ready or every live test skips, and it starts the live lane
    only after the offline suite passed, also under make -j. make test stays offline; run
    make check test for the former offline-only make verify. The deprecated CUBRID_PORT
    fallback is unchanged. make install now also installs the [pycubrid] extra, so the live
    lane can connect right after it. Development tooling only; the dialect API is unchanged.

Added

  • make verify writes test-results/verify/ (#1020) — after its phases, also after a
    failure, make verify writes summary.json with the overall PASS/FAIL/INCOMPLETE status
    and one entry per phase (check, test, integration). A phase that never started is
    NOT_RUN, and a missing or unreadable lane summary or an all-skipped live lane is never
    PASS. It also copies each lane's JUnit file to junit/ and the live lane's redacted
    environment.json, with configured passwords masked, and a file it cannot copy keeps the
    summary from PASS. The new scripts/run_verify.py runs the phases and forwards a SIGINT,
    SIGTERM or SIGHUP sent to make to the running phase, so make integration still cleans up.
    The new scripts/report_test_results.py aggregate subcommand builds the summary, and
    step-summary renders it. make verify now clears test-results/test/ and
    test-results/integration/ before it starts; make -n verify writes nothing.
  • make: run the live integration lane in make verify (#1045) (4d168ea)
  • make: write a verification summary under test-results/verify (#1047) (ac596a5)

CI

  • The make integration CI jobs publish the live results summary (#1021) — make-integration
    in ci.yml and integration-full.yml append test-results/integration/summary.json to the job
    summary with if: always(), so a failing or incomplete live lane shows its status and counts
    next to the uploaded pytest-logs-* artifact. No permission, secret or test-selection change.
  • Every new issue starts in status: needs triage (#1028) — the issue forms add the
    label, issue-triage.yml adds it to every opened issue instead of only to issues with
    incomplete titles or labels, and the upstream canary adds it to the issues it files. The
    unused scripts/check_issue_metadata.py check is removed. Priority and size are still set
    by a maintainer, who removes the label after triage.

Full Changelog: v1.11.7...v1.12.0