GitHub support for PHP Packages: “no longer planned”

by chunk_waffle on 6/7/2023, 4:06 PM with 4 comments
  • by pheouk on 6/7/2023, 6:43 PM

    Not just PHP, looks like they have the same token comment on PyPi, Helm and generic package support

  • by ezekg on 6/7/2023, 4:20 PM

    Composer makes it hard [0] to offer an artifact service for it because it authenticates per-domain, not per-package. For example, if you required 2 private packages from GitHub from php.pkg.github.com, you wouldn't be able to authenticate with both separately. You can only authenticate with php.pkg.github.com, not php.pkg.github.com/org-1/package and php.pkg.github.com/org-2/package.

    It's not ideal, but the workaround for this is to use subdomains:

    - org-1.php.pkg.github.com/package

    - org-2.php.pkg.github.com/package

    I wonder if that had any impact on their decision.

    [0]: https://github.com/keygen-sh/keygen-api/issues/490