@jmeshell Just curious what exactly "publishing releases to guest users" means? (Or maybe that's what we're trying to determine in this issue?) Our documentation mentions:
Guest users can access Release pages for downloading assets but are not allowed to download the source code nor see repository information such as tags and commits.
Does this satisfy the business need as described in this issue? It seems like this scenario has already been considered. Or are we thinking of opening up some of the information that's currently hidden to Guest users (such as source and tag/commit information)?
Regardless, I just gave this a try and this doesn't seem to work as described in our documentation above - I opened a new issue for this here: #198527 (closed)
Yeah, so this is sort of in a couple of parts/threads @nfriend:
In #26411, we see that there is an interest for a private project to have a "public" releases page to show that a release from a private project is now available
Private projects may add a guest user and want them to see the release page and nothing else in the private projects - this may be supported today as suggested by the documentation
It is possible that Guest Users are in fact experiencing the bug you found
@jmeshell Regarding #1: My reading of #26411 is that this is concerned with Guest access to a private project's release page, not necessarily making a fully public release page for private projects. Is this correct or am I misunderstanding?
I might comment on that issue and just mention the snippet from the documentation I linked to above.
In short, we e.g. need to publish Releases also internally to non-developer colleagues. They must be able to download and use the the software without having source code access.