Commit Graph

2 Commits (12fa0b7707b9ef81f8a9917c4f786cbd4d8eaabd)

Author SHA1 Message Date
David Sarno 12fa0b7707 Fix PyPI publish by inlining steps in release workflow
The pypa/gh-action-pypi-publish action does not support being called
from nested composite actions due to GitHub Actions context variable
limitations (github.action_repository not propagating correctly).

Inline the publish steps directly in release.yml to avoid the issue.
See: https://github.com/pypa/gh-action-pypi-publish/issues/338

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-14 16:09:27 -08:00
Marcus Sanatan 41664178aa
CI Updates (#536)
* Update the major tag of a version as well when publishing to Docker

Useful for the asset store releases

* feat: trigger publish workflows automatically after version bump and release creation

It should work in theory, and correctly release to Docker and pypi via tags.

* feat: consolidate release workflows into single pipeline with reusable actions

Refactored version bump, Docker publish, and PyPI publish workflows into a unified release pipeline that runs sequentially. Created reusable composite actions for Docker and PyPI publishing to eliminate duplication.

Changes:
- Rename bump-version.yml to release.yml with three jobs: bump, publish_docker, publish_pypi
- Create .github/actions/publish-docker/action.yml with configurable inputs for image, version, branch
2026-01-08 16:37:52 -04:00