acoustic-carpenter-78188
04/13/2026, 7:43 PMflytekitplugins_dask upload hung for 4 minutes during plugin publishing, then PyPI dropped the connection (RemoteDisconnected). This killed the entire deploy job, causing all Docker image builds to be skipped.
2. Re-runs are not idempotent: Re-running the failed workflow fails immediately because twine upload returns 400 Bad Request for already-uploaded packages.
3. build_image.yml passes github.sha as VERSION: The manual image build workflow passed the commit SHA as the PyPI version, which is not a valid PEP 440 version string, causing uv pip install flytekit==<sha> to fail.
4. Unstable Python version: actions/setup-python@v1 with python-version: "3.x" resolved to Python 3.14.3, which is brand new and potentially unstable for building release artifacts.
What changes were made?
pythonpublish.yml
• Upgrade actions/setup-python from v1 to v5
• Pin Python to 3.12 instead of 3.x
• Add --verbose --skip-existing to twine upload so re-runs skip already-uploaded packages
• Use safer shell parameter expansion (${GITHUB_REF#refs/tags/v}) instead of piping through sed
build_image.yml
• Add get-version job that extracts the semver from the branch/tag name (strips v prefix)
• All image build jobs now use the extracted version instead of github.sha as the VERSION build arg
• Add version-based image tags alongside SHA-based tags
plugins/Makefile
• Add --verbose --skip-existing to both twine upload commands
How was this tested?
Reviewed CI logs from the failed v1.16.17 release runs:
• https://github.com/flyteorg/flytekit/actions/runs/24267638003/attempts/1 (original failure - plugin upload connection error)
• https://github.com/flyteorg/flytekit/actions/runs/24267638003 (re-run failure - 400 already exists)
• https://github.com/flyteorg/flytekit/actions/runs/24358978725 (manual build_image failure - SHA as version)
Check all the applicable boxes
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
flyteorg/flytekitacoustic-carpenter-78188
04/13/2026, 7:49 PM