Skip to content
Snippets Groups Projects
  1. Nov 04, 2019
  2. Nov 01, 2019
  3. Oct 23, 2019
  4. Oct 17, 2019
  5. Oct 04, 2019
  6. Sep 18, 2019
  7. Sep 16, 2019
  8. Sep 03, 2019
  9. Jul 03, 2019
  10. May 03, 2019
    • Krasimir Angelov's avatar
      Allow guests users to access project releases · 241ba4be
      Krasimir Angelov authored
      This is step one of resolving
      https://gitlab.com/gitlab-org/gitlab-ce/issues/56838.
      
      Here is what changed:
      - Revert the security fix from bdee9e84.
      - Do not leak repository information (tag name, commit) to guests in API
      responses.
      - Do not include links to source code in API responses for users that do
      not have download_code access.
      - Show Releases in sidebar for guests.
      - Do not display links to source code under Assets for users that do not
      have download_code access.
      
      GET ':id/releases/:tag_name' still do not allow guests to access
      releases. This is to prevent guessing tag existence.
      241ba4be
  11. Apr 09, 2019
  12. Mar 28, 2019
  13. Jan 04, 2019
  14. Dec 31, 2018
  15. Dec 13, 2018
  16. Jul 26, 2018
  17. Oct 07, 2016
    • Nick Thomas's avatar
      Add markdown cache columns to the database, but don't use them yet · e94cd6fd
      Nick Thomas authored
      This commit adds a number of _html columns and, with the exception of Note,
      starts updating them whenever the content of their partner fields changes.
      
      Note has a collision with the note_html attr_accessor; that will be fixed later
      
      A background worker for clearing these cache columns is also introduced - use
      `rake cache:clear` to set it off. You can clear the database or Redis caches
      separately by running `rake cache:clear:db` or `rake cache:clear:redis`,
      respectively.
      e94cd6fd
  18. Jun 03, 2016
  19. May 09, 2016
  20. May 06, 2016
  21. Nov 13, 2015
  22. Nov 09, 2015
  23. Nov 06, 2015
  24. Nov 05, 2015
Loading