Dev release: <https://github.com/pantsbuild/pants/...
# development
w
Just a heads up to anyone using this, the new scie-pants that this requires isn't out yet. So, unless you're building from main, this won't work as expected
c
Should these just be a weekly cron?
Aspirationally, yes! But I don't know enough about how the GPG signing/tagging/releasing fits together.
w
Yeah I can set this up. There is no real enforcement of the gpg verification, other than in the local script. But, if you use the Github UI to do anything, you're automatically verified anyways. In general, it would be ideal if CI was doing the entire release, so we can have full build provenance and take humans out of the loop (other than probably kicking off non-dev releases). The existing dev release took 3 * 45 minutes of CI time, which was largely artificial