Fix PyPI publishing outside Python 2 container - #43
Merged
Conversation
Co-authored-by: polsala <15796004+polsala@users.noreply.github.com>
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
2 participants
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.
Summary
python:2.7-slimWhy
pypa/gh-action-pypi-publishdoes not support job-level containers. The previous workflow caused the runner's injected Python 3.14 binary to execute against the older glibc frompython:2.7-slim, failing before publication.Validation
git diff --checkdocker run --rm -v "$PWD:/src" -w /src python:2.7-slim python setup.py sdistdist/ooquery-0.23.0.tar.gzis generatedERP-ti task: not created because this host has no ERP-ti connection profile or credentials configured.
Requested by: @polsala
Follow-up to #41 and #42.