Releases are not visible to users with Guest Account
### Summary The Release page is empty with Guest Account on Omnibus Gitlab, even though releases exist in a project, and guests have access to releases. ### Steps to reproduce - Gitlab self hosted with Omnibus install (v12.4.0) - Create project - Create release on project - Add guest user access to project - Try to access release page with front ### Example Project Gitlab self hosted with Omnibus install (v12.4.0) ### What is the current *bug* behavior? Releases are not being displayed to guest users. ### What is the expected *correct* behavior? Releases should be displayed to guest users. ### Relevant logs and/or screenshots With API in Guest Account Token, we have one release: ![image](/uploads/a1ec09c1e636c29b3333cbc9c102ec6c/image.png) But empty page in front view with the same Guest Account ![image](/uploads/58be0e44026111eae7075aaf62a79bc6/image.png) No problem with Developer Account ![image](/uploads/4b3048a51b8ba74c07b78ce6377a0b4f/image.png) ### Output of checks (If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com) #### Results of GitLab environment info <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`) </pre> </details> #### Results of GitLab application Check <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)
issue