feat(ci): update publish pipeline for dual-package aignostics-sdk release [PYSDK-140]#651
Open
ari-nz wants to merge 1 commit into
Open
feat(ci): update publish pipeline for dual-package aignostics-sdk release [PYSDK-140]#651ari-nz wants to merge 1 commit into
ari-nz wants to merge 1 commit into
Conversation
…ease - Replace single uv publish step with sequential build+publish for aignostics-sdk (first) then aignostics (second) to respect dependency order - Add pre-publish lockstep version consistency check that fails fast if the two packages diverge - Add informational smoke_test_slim job (continue-on-error) that installs aignostics-sdk from PyPI after publish and asserts the CLI works, the slim import succeeds, and heavy deps (openslide) are absent - Update noxfile dist() session to build both packages into dist/ so make dist stays consistent with the new publish flow - GitHub release glob ./dist/* already covers both wheels since both are built into dist/
There was a problem hiding this comment.
Pull request overview
This PR updates the release pipeline to support publishing both the slim aignostics-sdk package and the full aignostics package in the upcoming workspace layout.
Changes:
- Adds lockstep version validation between the two package
pyproject.tomlfiles. - Replaces single-package publishing with package-specific build/publish steps.
- Adds a non-blocking PyPI smoke test for the slim SDK package.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.github/workflows/_package-publish.yml |
Updates release publishing for dual packages and adds the slim package smoke test. |
noxfile.py |
Updates the dist session to build both package distributions. |
Comment on lines
+189
to
+197
| - name: Publish aignostics-sdk to PyPI | ||
| shell: bash | ||
| env: | ||
| UV_PUBLISH_TOKEN: ${{ secrets.UV_PUBLISH_TOKEN }} | ||
| run: | | ||
| # Use uv's credential storage - uv will read from UV_PUBLISH_TOKEN env var automatically | ||
| uv publish | ||
| run: uv publish dist/aignostics_sdk-* | ||
|
|
||
| - name: Build aignostics distribution | ||
| shell: bash | ||
| run: uv build --package aignostics --out-dir dist/ |
This was referenced May 28, 2026
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.
Release Train — PYSDK-133
Summary
This PR updates the CI/CD publish pipeline to handle the new dual-package workspace structure introduced in PYSDK-133.
Changes
Sequential dual-package publish: Replaced the single
uv publishstep with a build-then-publish sequence for each package.aignostics-sdkis built and published first (required becauseaignosticsdepends on it), thenaignosticsis built and published second.Lockstep version consistency check: Added a pre-publish gate that reads the
version =field from bothpackages/aignostics-sdk/pyproject.tomlandpackages/aignostics/pyproject.tomland fails fast if they differ. This enforces the lockstep versioning contract before anything reaches PyPI.Slim package smoke test job: Added a new
smoke_test_slimjob (markedcontinue-on-error: trueso it does not gate the full package publish). Afterpackage_publishcompletes, this job installsaignostics-sdkfrom PyPI into a fresh venv, assertsaignostics-sdk --helpexits 0, verifiesfrom aignostics_sdk.platform import Clientworks, and confirms that heavy deps likeopenslideare absent.GitHub release artifact coverage: The existing
./dist/*glob in bothgh release createsteps already covers both wheels since all builds write intodist/. No change needed here.make dist/ noxfile update: Updated thedist()nox session to build both packages (uv build --package aignostics-sdk --out-dir dist/thenuv build --package aignostics --out-dir dist/) somake diststays consistent with the new publish flow.Test plan
python -c "import yaml; yaml.safe_load(open('.github/workflows/_package-publish.yml'))")package_publishjob builds and publishesaignostics-sdkbeforeaignosticssmoke_test_slimjob does not block the release on failure (continue-on-error: true)make distbuilds both packages once the workspace packages exist