All Versions
62
Latest Version
Avg Release Cycle
76 days
Latest Release
672 days ago

Changelog History
Page 1

  • v13.0.0 Changes

    August 15, 2022

    ๐Ÿ’ฅ Breaking Changes

    • 0๏ธโƒฃ The default serializer will now use YAML.safe_load unless ActiveRecord.use_yaml_unsafe_load. This change only affects users whose versions table has object or object_changes columns of type text, and who use the YAML serializer. People who use the JSON serializer, or those with json(b) columns, are unaffected. Please see [doc/pt_13_yaml_safe_load.md](doc/pt_13_yaml_safe_load.md) for details.

    โž• Added

    • None

    ๐Ÿ›  Fixed

    • None
  • v12.3.0 Changes

    March 13, 2022

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • #1371 - Added in_after_callback argument to PaperTrail::RecordTrail#save_with_version, to allow the caller to indicate if this method is being called during an after callback. Defaults to false.
    • #1374 - Added option --uuid when generating new migration. This can be used to set the type of item_id column to uuid for use with paper_trail on a database that uses uuid as primary key.

    ๐Ÿ›  Fixed

    • #1373 - Add CLI option to use uuid type for item_id when generating migration.
    • #1376 - Create a version record when associated object is touched. Restores the behavior of PaperTrail < v12.1.0.
  • v12.2.0 Changes

    January 21, 2022

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • #1365 - Support Rails 7.0
    • #1349 - if: and unless: work with touch events now.

    ๐Ÿ›  Fixed

    • #1366 - Fixed a bug where the create_versions migration lead to a broken db/schema.rb for Ruby 3

    Dependencies

    • #1338 - Support Psych version 4
    • ๐Ÿ’Ž ruby >= 2.6 (was >= 2.5). Ruby 2.5 reached EoL on 2021-03-31.
  • v12.1.0 Changes

    August 30, 2021

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • #1292 - where_attribute_changes queries for versions where the object's attribute changed to or from any values.
    • #1291 - where_object_changes_to queries for versions where the object's attributes changed to one set of known values from any other set of values.

    ๐Ÿ›  Fixed

    • #1285 - For ActiveRecord >= 6.0, the touch callback will no longer create a new Version for skipped or ignored attributes.
    • #1309 - Removes item_subtype requirement when specifying model-specific limits.
    • #1333 - Improve reification of STI models that use find_sti_class/sti_class_for to customize single table inheritance.
  • v12.0.0 Changes

    March 29, 2021

    ๐Ÿ’ฅ Breaking Changes

    • ๐Ÿš… #1281 Rails: Instead of an Engine, PT now provides a Railtie, which is simpler. This was not expected to be a breaking change, but has caused trouble for some people:
    • ๐Ÿ”ง Rails: The deprecated config.paper_trail configuration technique has been removed. This configuration object was deprecated in 10.2.0. It only had one key, config.paper_trail.enabled. Please review docs section 2.d. Turning PaperTrail Off for alternatives.

    โž• Added

    • where_object_changes_from queries for versions where the object's attributes changed from one set of known values to any other set of values.

    ๐Ÿ›  Fixed

    • ๐Ÿš… #1281 Rails: Instead of an Engine, PT now provides a Railtie, which is simpler.
    • Expand kwargs passed to save_with_version using double splat operator - Rails 6.1 compatibility
    • ๐Ÿš… #1287 - Fix 'rails db:migrate' error when run against an app with mysql2 adapter

    Dependencies

    • โฌ‡๏ธ Drop support for ruby 2.4 (reached EoL on 2020-03-31)
  • v11.1.0 Changes

    December 16, 2020

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • #1272 - Rails 6.1 compatibility

    ๐Ÿ›  Fixed

    • None
  • v11.0.0 Changes

    August 24, 2020

    ๐Ÿ’ฅ Breaking Changes

    • #1221 If you use the experimental association-tracking feature, and you forget to install the paper_trail-association_tracking gem, then, when you call track_associations= you will get a NoMethodError instead of the previous detailed error. Normally the removal of such a temporary warning would not be treated as a breaking change, but since this relates to PT-AT, it seemed warranted.
    • VersionConcern#sibling_versions is now private, and its arity has changed.

    โž• Added

    • None

    ๐Ÿ›  Fixed

    • #1242 - Generator make wrong migration for Oracle database

    • #1238 - Query optimization in reify

    • #1256 - Skip version for timestamp when changed attributed is ignored via Hash

    Dependencies

  • v10.3.1 Changes

    July 31, 2019

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • None

    ๐Ÿ›  Fixed

    • None

    Dependencies

    • #1213 - Allow contributors to install incompatible versions of ActiveRecord. See discussion in paper_trail/compatibility.rb
  • v10.3.0 Changes

    April 09, 2019

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • #1194 - Added a 'limit' option to has_paper_trail, allowing models to override the global PaperTrail.config.version_limit setting.

    ๐Ÿ›  Fixed

    • #1196 - In the installation migration, change versions.item_id from 4 byte integer to 8 bytes (bigint).
  • v10.2.1 Changes

    March 14, 2019

    ๐Ÿ’ฅ Breaking Changes

    • None

    โž• Added

    • None

    ๐Ÿ›  Fixed

    • #1184 - No need to calculate previous values of skipped attributes
    • #1188 - Optimized the memory allocations during the building of every particular Version object. That can help a lot for heavy bulk processing. In additional we advise to use json[b] DB types for object and object_changes Version columns, in order to reach best possible RAM performance.