Add BUILD-VERIFIED packaging check (no publish) - #22
Merged
Merged
Conversation
release_check.py runs the library dependency test, builds a wheel, and imports the new export from site-packages with PYTHONPATH stripped. GrokBot DevOps reads that JSON; it does not run python -m build. Co-authored-by: ale93.moro <ale93.moro@gmail.com>
When the working tree already matches origin/main, origin/main has no new symbol. Fall back to origin/main~1 so --json still finds the landed export without hardcoding a scheduler name. Skip local main — on a fork that ref may be upstream. Co-authored-by: ale93.moro <ale93.moro@gmail.com>
alex-16moro
marked this pull request as ready for review
September 20, 2026 18:26
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
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.
Summary
Add
tools/release_check.pyso a library checkout can prove a merged change produces an installable wheel. Verdict is BUILD-VERIFIED / PACKAGING-ELIGIBLE or NOT PACKAGING-ELIGIBLE. The wrapper does not publish, tag, twine-upload, or runmake pre-release.Steps, in order, against the fork checkout:
pytest tests/others/test_dependencies.py -qpython -m build --wheel(installbuildif needed; wipedist/first; record the exact wheel path)pip install --force-reinstall <that wheel>thenenv -u PYTHONPATHimport the new public export and assertdiffusers.__file__is under site-packagespip install -e .so the checkout stays usable--objectselects the export; if omitted, the new symbol is detected fromsrc/diffusers/__init__.pyvsorigin/main(ororigin/main~1when the tree already matches a just-landed merge). Advisories (changelog, semver,TODO(engineer)instep()) are FYI and never gate.GrokBot DevOps gains a Packaging section fed by
--release-jsonfrom that report. It does not runpython -m build. If the JSON is absent, the section printsnot wired.projections/devops/ci-gate.mdis regenerated fromtools/build_projections.py(make build).dist/is gitignored.Convention gate
make test(63 tests)make drift(generatedci-gate.mdmatches the generator)Tests run
Fork VERIFY on the PR #20 checkout (
cursor/pndm-lite-scaffold-2ce3, already landed on origin/main):Editable install restored (
pip install -e .).dist/is gitignored and not committed.Human judgment (not the gate)
python -m build, not a new product.step()math staysTODO(engineer).