build(py3): Stop tagging the -py3
images
#22470
Merged
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.
This is the final step in making the PY3 version the default for Docker images and self-hosted. It is part 5/5:
Add(ci(py3): Make py2 builds available under-py2
variants for the Python 2 build tags and introduce theSENTRY_PYTHON2
env variable usage-py2
suffix #22460)Switch getsentry/onpremise to Python 3 by default*, introducing the(ref(py3): Make PY3 the default*, add SENTRY_PYTHON self-hosted#763)SENTRY_PYTHON2
env var for Py2 builds via the-py2
suffixMove the unsuffixed version of the builds to Python 3(build(py3): Make PY3 images default (w/o suffix) #22466)Remove the(ref(py3): Remove SENTRY_PYTHON3 and -py3 versons self-hosted#764)SENTRY_PYTHON3
env var support and-py3
prefix usage from getsentry/onpremise-py3
builds from getsentry/sentry