Steven Silvester

Still no joy: `ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1133)`

I requested a Bluesky account using the Jupyter gmail account. Note: "Bluesky will launch soon. Join the waitlist to try the beta before it's publicly available."

Hi @ibdafna, yes, please, we still have not gotten a reply.

Thanks @ibdafna, done!

Thanks for the heads up, I don't have direct access so I'll bring it up to the EC. Note to self, instructions are here: https://blueskyweb.xyz/blog/4-28-2023-domain-handle-tutorial

I don't inderstand the need for multiple instances here, why not override the server end instance with an extension to provide the extra capabilities?

That's fair, thanks for clarifying.

JupyterLab Git has some dry run logic for both [pypi](https://github.com/jupyterlab/jupyterlab-git/blob/8d56986409461cd9968d7208da4946fca8c70392/release.py#L25) and npm. We don't necessarily need to pull from the test servers, we could have two release targets.

I prefer "very hacky and pragmatic" :smile:

If we adopted an "only move forward approach" where there is no 2.x minor release after a 3.x release, then we could avoid the hacky approach. The hacky approach was...