Keep ActiveRecord version in attr_encrypted in sync with gitlab-rails
The following discussion from !98528 (merged) should be addressed:
-
@mkaeppler started a discussion: (+1 comment) I dropped the conditional that was here before and which controlled this dependency via an environment variable since it caused pain in the CI setup.
We need to keep in mind that this should remain in lockstep with the main
Gemfile
. Any ideas how to best do that? Maybe for now just leave a comment in the main Gemfile to also bump this whenever we update AR?
attr_encrypted is now vendored into gitlab-rails and it uses an ActiveRecord extension that can break across AR updates.
Aside from code comments, can we think of a mechanism that keeps these versions in lockstep? Perhaps emitting a bundler message when the AR gem is updated?