Changeset values different when called from `item`.

[joshuapinter]

Check the following boxes:

• This is not a usage question, this is a bug report
• This bug can be reproduced with the script I provide below
• This bug can be reproduced in the latest release of the paper_trail gem

I'm happy to look into this and fix it, along with other PRs I have created but want to get your initial opinion to help put me on the right track.

I am seeing two different results when calling changeset for the same version record. Here is a simplified version:

version.id
#=> 66759735

version.changeset
#=> 
{ "file_file_name" =>
  ["CNTRAL - Black Swan Energy Report - Black Swan Energy - 2021-01-14 07-14-53.pdf",
   "CNTRAL - Black Swan Energy Report - Black Swan Energy - 2021-01-14 07-14-53.pdf"]}

version.item.versions.last.id
#=> 66759735

version.item.versions.last.changeset
# => 
{ "file_file_name" =>
  ["CNTRAL - Black Swan Energy   Report - Black Swan Energy - 2021-01-14 07-14-53.pdf",
   "CNTRAL - Black Swan Energy Report - Black Swan Energy - 2021-01-14 07-14-53.pdf"]}

Again, happy to fix this if you can point me in the right direction.

Thanks!

[github-actions]

This issue has been automatically marked as stale due to inactivity.
The resources of our volunteers are limited.
Bug reports must provide a script that reproduces the bug, using our template. Feature suggestions must include a promise to build the feature yourself.
Thank you for all your contributions.

[joshuapinter]

This is still an issue. Again, I'm happy to submit a PR issue if somebody on the core team shows an interest in reviewing this and getting it merged in. Just let me know. Thanks.

[github-actions]

This issue has been automatically marked as stale due to inactivity.
The resources of our volunteers are limited.
Bug reports must provide a script that reproduces the bug, using our template. Feature suggestions must include a promise to build the feature yourself.
Thank you for all your contributions.

[joshuapinter]

Still an issue. Happy to look at fixing it. Please let me know.

[github-actions]

This issue has been automatically marked as stale due to inactivity.
The resources of our volunteers are limited.
Bug reports must provide a script that reproduces the bug, using our template. Feature suggestions must include a promise to build the feature yourself.
Thank you for all your contributions.

[joshuapinter]

This is still an issue. @fatkodima Let me know if you want this fixed and I can make time to do this. Thanks!

[github-actions]

This issue has been automatically marked as stale due to inactivity.
The resources of our volunteers are limited.
Bug reports must provide a script that reproduces the bug, using our template. Feature suggestions must include a promise to build the feature yourself.
Thank you for all your contributions.

[joshuapinter]

Happy to make this fix and change. Should be pretty easy and adds consistency. Just let me know.