Repository navigation
Release CI follow-ups: tighter coverage #747
Description
Follow-ups identified during code review of #745. Not blocking, but worth doing.
Files / scripts
- Rename
examples/deep-researcher/utils.py— currently shares its basename with 4 other ASF-ownedutils.pyfiles. The new.rat-excludesuses basename matching, so all 5 are skipped. A future regression in any of the 4 ASF files would silently pass RAT. - Thread
--skip-signingthroughcmd_verifyinscripts/apache_release.py. Today running theverifysubcommand against a--skip-signingbuild crashes on missing.ascfiles. - Run RAT on the wheel too, not just the tarballs. Wheel is also redistributed.
- Pin the RAT JAR by SHA256 in
.github/workflows/release-validation.yml. Currently the workflow downloads from Maven Central without integrity verification.
Smoke test (scripts/ci_smoke_server.py)
- Replace
time.sleep(2)after running the tracked app with a poll-then-assert loop on/api/v0/projects(currently flake-prone). - Forward
SIGTERMto the uvicorn child via process group (currently only kills the burr CLI wrapper; child can be orphaned on dev boxes). - Add
--cleanupflag and default to cleaning the workspace locally (CI keeps it viaGITHUB_ACTIONSenv, currently always retained).
CI coverage gaps
- Add a matrix cell that does bare
pip install <wheel>(no[learn]extras) and at least importsburrandburr.tracking.server.run. Catches optional-extra dep leakage into base. - Add a step that builds the wheel from the sdist tarball (what voters do) and asserts the result matches the CI-built wheel. Catches sdist-vs-wheel drift.
- Hit
GET /in the smoke test to confirm the UI build is actually served (not just present in the wheel).
Hygiene
- Add a pre-commit hook that grep-checks new files for ASF headers (RAT in CI is the safety net but slow).
- Add a weekly cron job running this workflow against
mainto catch dep-drift between RCs.
Activity
andreahlert commentedon Apr 23, 2026
This issue is a follow-up of #745 and part of the release process automation epic #715.
github-actions commentedon May 13, 2026
@elijahbenizzy, this issue has been inactive for 19 days.
Are you still working on it? Drop a comment to let us know.
If there is no update within 7 days, the assignment will be removed
so someone else can pick it up
(per the assignment policy).
github-actions commentedon May 27, 2026
@elijahbenizzy, this issue has been inactive for 14 days.
Are you still working on it? Drop a comment to let us know.
If there is no update within 7 days, the assignment will be removed
so someone else can pick it up
(per the assignment policy).
github-actions commentedon Jun 10, 2026
@elijahbenizzy, this issue has been inactive for 14 days.
Are you still working on it? Drop a comment to let us know.
If there is no update within 7 days, the assignment will be removed
so someone else can pick it up
(per the assignment policy).
t1mato commentedon Jun 23, 2026
Hello, would love to work on this issue if it hasn't been finished already.
@elijahbenizzy @andreahlert
github-actions commentedon Jul 8, 2026
@elijahbenizzy, @t1mato, this issue has been inactive for 14 days.
Are you still working on it? Drop a comment to let us know.
If there is no update within 7 days, the assignment will be removed
so someone else can pick it up
(per the assignment policy).
ci: add files/scripts
ci: add smoke test improvements
ci: add CI coverage gaps
ci: add hygiene improvements
ci: release CI follow-ups: tighter coverage (#832)