Repository navigation
ci: publish runtime source assets with GitHub releases - #12
Conversation
KAJdev
changed the title
| uses: pypa/gh-action-pypi-publish@release/v1 | ||
| if: steps.release.outputs.release_created == 'true' || inputs.release_tag != '' | ||
|
|
||
| - name: Publish runtime release asset |
There was a problem hiding this comment.
nit: with the PyPI job gone, the README's Releases section ("A release publishes the Python package and versioned Docker images") no longer matches. Could it say the release attaches runpod-sdk-runtime.tar.gz as a stable-named asset that the SDK and task shims install from releases/latest, and mention the release_tag dispatch for finishing a stuck draft?
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are recorded for the release-archive publishing changes.
No open issues 🎉
What changed in this PR
This PR publishes a stable-named runtime source archive with GitHub releases for SDK and production task bootstrapping. Releases remain drafts until the archive is uploaded, then publish to trigger image builds.
Changes:
- Configure release-please to create draft releases and force tag creation.
- Replace PyPI publishing with uploading
runpod-sdk-runtime.tar.gz, then publish the release. - Serialize release runs and add a manual tag input to finish interrupted draft releases.
| File | Description |
|---|---|
release-please-config.json |
Enable draft releases and forced tag creation. |
.github/workflows/release.yml |
Build and upload the source archive before publishing, with manual recovery and concurrency control. |
Review effort: Balanced
Publish a stable-named runtime source archive on each GitHub release for SDK and production task bootstrapping. Keep releases in draft until the asset is uploaded, then publish them to trigger image builds. Manual dispatch can finish an interrupted draft release.