-
Jean Boussier authored
Fix: https://github.com/rails/rails/issues/53710 Fix: https://github.com/rails/rails/pull/54290 The Rails 7.1 to 7.2 upgrade can be very complicated if you use Active Record's `find_signed` feature, as its MessageVerifier switched from regular Base64 encoding to URL-safe Base64 encoding, making all previously generated ids invalid. To ease the transition, MessageVerifier's `url_safe` option now only control which encoding method is used to generate messages, for decoding them both are always valid. Co-Authored-By:
Ali Sepehri <ali.khameneh@doctolib.com> Co-Authored-By:
Florent Beaurain <florent.beaurain@doctolib.com>
Jean Boussier authoredFix: https://github.com/rails/rails/issues/53710 Fix: https://github.com/rails/rails/pull/54290 The Rails 7.1 to 7.2 upgrade can be very complicated if you use Active Record's `find_signed` feature, as its MessageVerifier switched from regular Base64 encoding to URL-safe Base64 encoding, making all previously generated ids invalid. To ease the transition, MessageVerifier's `url_safe` option now only control which encoding method is used to generate messages, for decoding them both are always valid. Co-Authored-By:
Loading