Latest Common-Lisp.net news
NOTE: The new host has stricter SSH key requirements than the old one, so for example older, weaker RSA keys may no longer work. We don't plan to enable support for legacy keys which are considered insecure by today's standards. If this appears to affect you, please generate a new keypair (RSA, ED25519) and send the public key to the clo-devel mailing list (which we assume you're already on if you had ssh access to the old host), or ask for support at the IRC channel noted in the previous News item.
The toplevel common-lisp.net domain (which you're presumably looking at right now) has been changed to point to our new host, the same as gitlab.common-lisp.net and future.common-lisp.net. Most ssh user accounts (with intact UIDs) and their home directories were copied to the new host in late December, 2024. If you need to synchronize any interim changes from the old host, you should be able to use rsync and you can access the old host with your existing ssh key at e.g. legacy.common-lisp.net (any default *.common-lisp.net is still pointing to the old host). You may need to update your ~/.ssh/config accordingly to point to the legacy hostname.
Gitlab has been moved to a new host. Other services will follow to this new host. Please update your remotes to use gitlab.common-lisp.net if they were using bare common-lisp.net previously. Follow discussion of server migration at the #common-lisp.net channel on libera.chat IRC.
All project sites have moved from https://common-lisp.net/project/<project-name> to https://<project-name>.common-lisp.dev. The former now redirects to the latter, so bookmarks should continue to work. Additionally, we have added new content to our FAQs on how to deploy a website to https://<project-name>.common-lisp.dev, as well as use GitLab CI for testing and more complicated tasks.