SE-0292, which is currently in review, proposes an alternative solution to the problem of monorepos, by allowing maintainers to specify a path
when publishing package releases to a registry. Quoting from the specification:
4.5.5. Package location
A client MAY use
path
andurl
parameters together to publish a single package located in a subdirectory of a repository or to publish multiple packages from different paths in a single repository.If a client specifies a
path
parameter, a server SHOULD look for aPackage.swift
file at that location. Otherwise, it SHOULD look at the root directory. If aPackage.swift
file doesn't exist at that location, a server SHOULD respond with a status code of404
(Not Found).
Would this be a reasonable solution to the problems you've identified here?