Skip to content

ci: build + attach wheel/sdist to GitHub release (drop PyPI publishing)#21

Merged
RatulMaharaj merged 2 commits into
mainfrom
ci/attach-wheel-to-github-release
Jun 25, 2026
Merged

ci: build + attach wheel/sdist to GitHub release (drop PyPI publishing)#21
RatulMaharaj merged 2 commits into
mainfrom
ci/attach-wheel-to-github-release

Conversation

@RatulMaharaj

@RatulMaharaj RatulMaharaj commented Jun 25, 2026

Copy link
Copy Markdown
Collaborator

Why

The DataMaker desktop runner pins datamaker-py by source-archive URL (/archive/<sha>.tar.gz), an sdist that uv/pip must build at install time. That build is what blocks the desktop app from provisioning its Python venv fully offline.

What

  • On a published release, uv build and attach the wheel + sdist as GitHub release assets. Consumers pin a direct .whl URL:
    datamaker-py @ https://github.com/automators-com/datamaker-py/releases/download/<tag>/datamaker_py-<ver>-py3-none-any.whl
    
    URL ends in .whl → installs as a wheel, no build step. Repo is public → no auth.
  • Removed the PyPI trusted-publishing job entirely (project isn't on PyPI; standardizing on GitHub release assets).

Next

  1. Merge → cut release v0.7.0 (wheel attaches automatically).
  2. Re-pin the runner to the release .whl URL + regenerate the lock → runtime does zero building.

🤖 Generated with Claude Code

RatulMaharaj and others added 2 commits June 25, 2026 17:09
On a published release, upload the `uv build` artifacts (wheel + sdist) as
release assets so consumers can pin a direct `.whl` URL:

  datamaker-py @ https://github.com/automators-com/datamaker-py/releases/download/<tag>/datamaker_py-<ver>-py3-none-any.whl

Because the URL ends in `.whl`, uv/pip install it as a wheel with no build step
— the DataMaker desktop runner needs this to provision its venv fully offline
(URL-locked sdists currently force a build at install time). The repo is public,
so the asset URL needs no auth.

Also gate the existing PyPI publish job behind `vars.PUBLISH_TO_PYPI == 'true'`:
PyPI trusted publishing isn't set up yet (the project isn't on PyPI), so the job
would fail on every release. It's now opt-in until configured.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TMwtcrQZ2WSMZB7wZYM6za
On a published release, build with `uv build` and upload the wheel + sdist as
GitHub release assets, so consumers can pin a direct `.whl` URL and install with
no build step (the desktop runner provisions its venv fully offline this way).

Removes the PyPI trusted-publishing job entirely: the project isn't on PyPI and
we're standardizing on GitHub release assets.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TMwtcrQZ2WSMZB7wZYM6za
@RatulMaharaj RatulMaharaj changed the title ci: attach built wheel + sdist to the GitHub release ci: build + attach wheel/sdist to GitHub release (drop PyPI publishing) Jun 25, 2026
@RatulMaharaj RatulMaharaj merged commit 5b9342f into main Jun 25, 2026
4 checks passed
@RatulMaharaj RatulMaharaj deleted the ci/attach-wheel-to-github-release branch June 25, 2026 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant