Have we discussed the release failures for 2.17.x ...
# development
b
Have we discussed the release failures for 2.17.x and 2.16.x yet?
ImportError: urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with 'OpenSSL 1.0.2k-fips 26 Jan 2017'. See: https://github.com/urllib3/urllib3/issues/2168
https://github.com/pantsbuild/pants/actions/runs/6286002410/job/17070047264 https://github.com/pantsbuild/pants/actions/runs/6286401038/job/17069772062
Looks like it's an invocation of
twine
Let's see if downgrading
urllib3
works
Will make PRs shortly
(unless someone else has a suggestions regarding upgrading something transient in the container to be compatible)
I think this has to do with Python 3.7, since this doesn't error on 2.18+, and doesn't error for Py39 in these releases
Well I guessed the only real thing that changed was the
manylinux
container image (since we just use
:latest
) And sure enough, pinning the label to the version we used for
2.17.0
release (~August) worked
I'll make that PR
b
Thanks for making the fixes. Does this mean the releases that were failing have now succeeded? Or should I be cutting new releases? (2.16.1rc1 and 2.17.1rc1, I think?)
Ah, no, next would be 2.16.1.rc3
b
I'm not sure, honestly on 2.16, because I don't see tags for rc1 or rc2
2.17 yes do the next one
I can probably make the 2.16 releases exist, so don't do rc3 unless there's changes
c
where are we with the 2.16 release now? I feel bad for just abandoning it, so if there’s something needs to be done with it, I can dig into it.
b
Can you push the tags? I think that's all that's needed
👍 1
c
I think we can ignore 2.16.1rc1.. the rc2 is mostly a retry of a failed release of rc1
pushed the rc2 tag now.
b
I mean no harm in tagging? But okie dokie. I'll try and get rc2 tonight if I can
👍 1
c
sure, I’ll tag it just to plug the tag-hole…
done