Does Github package registry support Swift Package Registry Service

[ghost]

Will GitHub Packages support Swift Package Registry Service anytime soon?

Here is a blog post from 2019, but I still can't find this option available.
https://github.blog/2019-06-03-github-package-registry-will-support-swift-packages/

Swift Package Registry Service: https://github.com/apple/swift-evolution/blob/main/proposals/0292-package-registry-service.md

[ossanna16]

Hey there @amrndic and thank you for asking a good question! I'm glad you found our community 🙂

[hollyoops]

Is there any update for this?

[vmanot]

I'd love to know as well!

[hollyoops]

Same question here. we need to integrate SPM on Jfrog. Jfrog need to specify a package registry URL.

Dose Github support the Swift Package Registry? if dose how do I use it?

[erichoracek]

We're also very interested in support for this now that Swift 5.7 is released and the package registry service proposal is implemented

[hollyoops]

I can‘t wait. So I just implemented it by myself on top of api.github.com. One issue I meet is I can't get the checksum value until I download it.

Ex: I need to download a zip file according to a release. But before that we need to get meta data first like this

  "resources": [
    {
      "name": "source-archive",
      "type": "application/zip",
      "checksum": "a2ac54cf25fbc1ad0028f03f0aa4b96833b83bb05a14e510892bb27dea4dc812"
    }

There is no way to get the zip checksum before downloading.

[hollyoops]

I implemented a simple one: https://github.com/hollyoops/swiftPM-registry-service

Looking forward, the official support from GitHub

[0xpablo]

AWS recently added support for the Swift Package Registry Service to AWS CodeArtifact.
It'd be great if GitHub added support as well, as most of the community uses GitHub to resolve swift packages and this would alleviate performance issues when fetching and resolving packages.

[tomisacat]

https://docs.github.com/en/packages Obviously, nope : (

[vmanot]

Would love to know about the status of this.

At the very least, the blog post should be updated to reflect the fact that this has not materialized (It's been 3 years since it was last updated).