Upgrading rails 5.0 to 5.2 in production environment causes incorrect asset fingerprint

Question

I recently upgraded a rails 5.0 app to 5.2, running Puma 3.0. I am using capistrano 1.3.0 to deploy. This bug was not occurring before I ran the upgrade.

When I load