Is It the Year of Swift on the Server?

This last year has been all about documentation. We shipped the first version of DocC documentation generation support on the package index. As your packages move forward through releases and especially major releases, we update the documentation every time you release a package. So when you make breaking API changes, which generally get indicated by a major version change, we'll keep that old version around for you. And again, all of that just happens completely automatically. Like literally you don't need to do anything apart from the term targets. But of course, to provide that level of simplicity for the end user, and also for the package author, there's an enormous amount of work.