There is a tag for the release, called swift-3.1-RELEASE: https://github.com/apple/swift/tree/swift-3.1-RELEASE https://github.com/apple/swift/tree/swift-3.1-R

There is a tag for the release, called swift-3.1-RELEASE: https://github.com/apple/swift/tree/swift-3.1-RELEASE https://github.com/apple/swift/tree/swift-3.1-RELEASE It's not showing up on GitHub's UI nor search for me at present, which may be why it seems like it's missing. You can download a .tgz from GitHub but bear in mind that you have to do the same for each of the nested repositories as well. If you're building it for yourself, it's easier to download the swift-3.1-RELEASE content, and then run 'utils/update-checkout --clone --skip-history --tag swift-3.1-RELEASE' to procure the rest of the repositories. There are a number of bugs to work on Swift packages for RHEL/CentOS: https://bugs.swift.org/browse/SR-100 https://bugs.swift.org/browse/SR-100 https://bugs.swift.org/browse/SR-108 https://bugs.swift.org/browse/SR-108 https://bugs.swift.org/browse/SR-116 https://bugs.swift.org/browse/SR-116 The issues are primarily around those operating systems having too old a version of Clang in their default repositories to be able to bootstrap the newer builds, and the fact that they don't have the blocks runtime available, both of which are used by the Swift runtime.