Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

Scheduled maintenance on the database layer will take place on 2022-07-02. We expect GitLab.com to be unavailable for up to 2 hours starting from 06:00 UTC. Kindly follow our status page for updates and read more in our blog post.

  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #48392
Closed
Open
Created Jun 25, 2018 by Jan Provaznik@jprovaznik🔴Maintainer

[Rails5] Upgrade to 5.2

Currently in Gemfile we use Rails 5.0.7, but to avoid multiple bigger upgrades, we should investigate how much effort it takes make GitLab working ideally with 5.2, and if this is too much effort how difficult it would be to upgrade to 5.1.

We should also:

  • fix lograge to play with Rails 5.2 properly: https://github.com/roidrage/lograge/issues/266 (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20630#note_137903623)
  • consider updating activesupport in gitaly simultaneously (https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8877#note_127482919)
Edited Feb 05, 2019 by Jan Provaznik
Assignee
Assign to
Time tracking