All Versions
61
Latest Version
Avg Release Cycle
70 days
Latest Release
106 days ago

Changelog History
Page 2

  • v10.1.0 Changes

    December 04, 2018

    ๐Ÿ’ฅ Breaking Changes

    • None

    ๐Ÿ—„ Deprecated

    • #1158 - Passing association name as versions: option or Version class name as class_name: options directly to has_paper_trail. Use has_paper_trail versions: {name: :my_name, class_name: "MyVersionModel"} instead.

    โž• Added

    • #1166 - New global option has_paper_trail_defaults, defaults for has_paper_trail
    • #1158 โ€” Add the ability to pass options, such as scope or extend: to the has_many :versions association macro.
    • #1172 - Support rails 6.0.0.alpha

    ๐Ÿ›  Fixed

    • None
  • v10.0.1 Changes

    September 01, 2018

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • None

    ๐Ÿ›  Fixed

    • #1150 - When PT-AT is not loaded, and someone sets track_associations = false, it should warn, not raise.
  • v10.0.0 Changes

    September 01, 2018

    ๐Ÿ›  PT 10 tackles some tough issues that required breaking changes. We fixed a rare issue with STI, and saved major disk space in databases with tens of millions of version records. Special thanks to @lorint and @seanlinsley, respectively.

    ๐Ÿ’ฅ Breaking changes affecting most people

    • ๐Ÿšš #1132 - Removed a dozen methods deprecated in PT 9. Make sure you've addressed all deprecation warnings before upgrading.

    ๐Ÿ’ฅ Breaking changes affecting fewer people

    • db9c392d - paper_trail-association_tracking is no longer a runtime dependency. If you use it (track_associations = true) you must now add it to your own Gemfile. See also PT-AT #7
    • #1130 - Removed save_changes. For those wanting to save space, it's more effective to drop the object column. If you need ultimate control over the object_changes column, you can write your own object_changes_adapter.

    ๐Ÿ’ฅ Breaking changes most people won't care about

    • #1121 - touch now always inserts null in object_changes.
    • #1123 - object_changes is now populated on destroy in order to make where_object_changes usable when you've dropped the object column. Sean is working on an optional backport migration and will post about it in #1099 when he's done.

    โž• Added

    • #1099 - Ability to save ~50% storage space by making the object column optional. Note that this disables reify and where_object.

    ๐Ÿ›  Fixed

    • #594 - A rare issue with reification of STI subclasses, affecting only PT-AT users who have a model with mutliple associations, whose foreign keys are named the same, and whose foreign models are STI with the same parent class. This fix requires a schema change. See docs section 4.b.1 The optional item_subtype column for instructions.
  • v9.2.0 Changes

    June 09, 2018

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • #1070 - The experimental associations tracking feature has been moved to a separate gem, paper_trail-association_tracking. PT will, for now, have a runtime dependency on this new gem. So, assuming the gem extraction goes well, no breaking changes are anticipated.
    • #1093 - PaperTrail.config.object_changes_adapter - Expert users can write their own adapter to control how the changes for each version are stored in the object_changes column. An example of this implementation using the hashdiff gem can be found here: paper_trail-hashdiff

    ๐Ÿ›  Fixed

    • None
  • v9.1.1 Changes

    May 30, 2018

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • None

    ๐Ÿ›  Fixed

    • #1098 - Fix regression in 9.1.0 re: generator --with-associations
  • v9.1.0 Changes

    May 23, 2018

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • #1091 - PaperTrail.config.association_reify_error_behaviour - For users of the experimental association tracking feature. Starting with PT 9.0.0, reification of has_one associations is stricter. This option gives users some choices for how to handle the PaperTrail::Reifiers::HasOne::FoundMoreThanOne error introduced in PT 9. See README section 4.b.1. "Known Issues" for more details.

    ๐Ÿ›  Fixed

    • None
  • v9.0.2 Changes

    May 14, 2018

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • None

    ๐Ÿ›  Fixed

    • #1084 The touch callback (added in 9.0.0) now inserts the correct value into the versions.object column.

    Other

    • โœ… Stop testing against rails 5.0, which reached EoL on 2018-04-15, when 5.2 was released, per the rails maintenance policy
  • v9.0.1 Changes

    April 23, 2018

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • #1076 Add save_with_version, a replacement for deprecated method touch_with_version. Not exactly the same, it's a save, not a touch.
    • #1074 PaperTrail.request do ... end now returns the value the given block.

    ๐Ÿ›  Fixed

    • None
  • v9.0.0 Changes

    March 26, 2018

    ๐Ÿ’ฅ Breaking Changes, Major

    • #1063 - touch will now create a version. This can be configured with the :on option. See documentation section 2.a. "Choosing Lifecycle Events To Monitor".
    • โฌ‡๏ธ Drop support for ruby 2.2, whose EoL is the end of March, 2018
    • PaperTrail now uses frozen_string_literal, so you should assume that all strings it returns are frozen.
    • Using where_object_changes to read YAML from a text column will now raise error, was deprecated in 8.1.0.

    ๐Ÿ’ฅ Breaking Changes, Minor

    • Removed deprecated Version#originator, use #paper_trail_originator
    • Using paper_trail.on_destroy(:after) with ActiveRecord's belongs_to_required_by_default will produce an error instead of a warning.
    • Removed the warn_about_not_setting_whodunnit controller method. This will only be a problem for you if you are skipping it, eg. skip_after_action :warn_about_not_setting_whodunnit, which few people did.

    ๐Ÿ—„ Deprecated

    • #1063 - paper_trail.touch_with_version is deprecated in favor of touch.
    • #1033 - Request variables are now set using eg. PaperTrail.request.whodunnit= and the old way, PaperTrail.whodunnit= is deprecated.

    โž• Added

    • #1067 - Add support to Rails 5.2.
    • #1033 - Set request variables temporarily using a block, eg. PaperTrail.request(whodunnit: 'Jared') do .. end
    • #1037 Add paper_trail.update_columns
    • #961 - Instead of crashing when misconfigured Custom Version Classes are used, an error will be raised earlier, with a much more helpful message.
    • Failing to set PaperTrail.config.track_associations will no longer produce a warning. The default (false) will remain the same.

    ๐Ÿ›  Fixed

    • #1051 - touch_with_version should always create a version, regardles of the :only option
    • #1047 - A rare issue where touch_with_version saved less data than expected, but only when the update callback was not installed, eg. has_paper_trail(on: [])
    • #1042 - A rare issue with load order when using PT outside of rails
    • #594 - Improved the error message for a very rare issue in the experimental association tracking feature involving two has_one associations, referencing STI models with the same base class, and the same foreign_key.
  • v8.1.2 Changes

    December 22, 2017

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • None

    ๐Ÿ›  Fixed

    • #1028 Reifying associations will now use base_class name instead of class name to reify STI models corrrectly.