Update dependency ancestry to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ancestry (changelog)	"~>4.1.0" → "~>5.1.0"

---

Release Notes

stefankroes/ancestry (ancestry)

v5.1.0

Compare Source

• update_strategy: :sql now works on all databases (SQLite, MySQL, PostgreSQL) #​715
• Introduce depth constraint validation for subtree moves #​713 (thx @​wilburhimself)
• Fix: CHANGELOG HTML entity fix #​712 (thx @​biow0lf)
• Testing Ruby 4.0 support #​709 (thx @​fkmy)
• Tested against Ruby 2.7–4.0 and Rails 6.0–8.1 #​716

Deprecations

These class-level accessors still work but are being phased out.
We are moving configuration into baked method bodies and away from class variables.
If you depend on reading these at runtime, now is a good time to find alternatives:

• ancestry_column, ancestry_delimiter, depth_cache_column, counter_cache_column, touch_ancestors

Breaking Changes

• sort_by_ancestry and check_ancestry_integrity! now delegate to _sort_by_ancestry and
  _check_ancestry_integrity! with an explicit column parameter. The public API is unchanged.

v5.0.0

Compare Source

• Fix: siblings now excludes self #​710 (thx @​chikamichi)
• Introduce orphan_strategy: :none #​658
• Introduce rebuild_counter_cache! to reset counter caches. #​663 #​668 (thx @​RongRongTeng)
• Introduce in_subtree_of? instance method #​680 (thx @​instrumentl)
• Optimize has_siblings? to use exists? #​693 (thx @​a5-stable)
• Fix: humanise model name in error messages #​700 (thx @​labeebklatif)
• Fix: touch with sql update strategy
• Introduce update_strategy: :sql hooks for extension developers
• Added support for virtual depth column
• Documentation fixes #​664 #​667 (thx @​motokikando, @​onerinas)
• Introduce build_cache_depth_sql!, a sql alternative to build_cache_depth #​654
• Drop ancestry_primary_key_format #​649
• When destroying orphans, going from leafs up to node #​635 (thx @​brendon)
• Changed config setters to class readers #​633 (thx @​kshurov)
• Split apply_orphan_strategy into multiple methods #​632 #​633
• Ruby 3.4 support
• Rails 8.0 support

Notable features

Depth scopes now work without cache_depth. But please only use this in background
jobs. If you need to do this in the ui, please use cache_depth.

build_cache_depth_sql! is quicker than build_cache_depth! (1 query instead of N+1 queries).

Deprecations

• Option :depth_cache_column is going away.
  Please use a single key instead: cache_depth: :depth_cach_column_name.
  cache_depth: true still defaults to ancestry_depth.

Breaking Changes

• siblings no longer returns self. This is a bug fix, but does change behavior.
• Dropped support for Rails < 6.1
• Renamed internal methods to follow Rails conventions: *_before_save methods renamed to *_before_last_save
  (e.g., child_ancestry_before_save => child_ancestry_before_last_save)
• Options are no longer set via class methods. Using has_ancestry is now the only way to enable these features.
  These are all not part of the public API.
  • These are now class level read only accessors
    • ancestry_base_class (introduced 1.1, removed by #​633)
    • ancestry_column (introduced 1.2, removed by #​633)
    • ancestry_delimiter (introduced 4.3.0, removed by #​633)
    • depth_cache_column (introduced 4.3.0, removed by #​654)
  • These no longer have any accessors
    • ancestry_format (introduced 4.3.0, removed by #​654)
    • orphan_strategy (introduced 1.1, removed by #​617)
    • ancestry_primary_key_format (introduced 4.3.0, removed by #​649)
    • touch_ancestors (introduced 2.1, removed by TODO)
• These are seen as internal and may go away:
  • apply_orphan_strategy Please use orphan_strategy: :none and a custom before_destory instead.

v4.3.3

Compare Source

• Fix: sort_by_ancesty with custom ancestry_column #​656 (thx @​mitsuru)

v4.3.2

Compare Source

• Fix: added back fields that were removed in #​589 #​647 (thx @​rastamhadi)
  • path_ids_in_database

v4.3.1

Compare Source

• Fix: added back fields that were removed in #​589 #​637 (thx @​znz)
  • ancestor_ids_in_database
  • parent_id_in_database

v4.3.0

Compare Source

• Fix: siblings now excludes self #​710 (thx @​chikamichi)
• Introduce orphan_strategy: :none #​658
• Introduce rebuild_counter_cache! to reset counter caches. #​663 #​668 (thx @​RongRongTeng)
• Introduce in_subtree_of? instance method #​680 (thx @​instrumentl)
• Optimize has_siblings? to use exists? #​693 (thx @​a5-stable)
• Fix: humanise model name in error messages #​700 (thx @​labeebklatif)
• Fix: touch with sql update strategy
• Introduce update_strategy: :sql hooks for extension developers
• Added support for virtual depth column
• Documentation fixes #​664 #​667 (thx @​motokikando, @​onerinas)
• Introduce build_cache_depth_sql!, a sql alternative to build_cache_depth #​654
• Drop ancestry_primary_key_format #​649
• When destroying orphans, going from leafs up to node #​635 (thx @​brendon)
• Changed config setters to class readers #​633 (thx @​kshurov)
• Split apply_orphan_strategy into multiple methods #​632 #​633
• Ruby 3.4 support
• Rails 8.0 support

Notable features

Depth scopes now work without cache_depth. But please only use this in background
jobs. If you need to do this in the ui, please use cache_depth.

build_cache_depth_sql! is quicker than build_cache_depth! (1 query instead of N+1 queries).

Deprecations

• Option :depth_cache_column is going away.
  Please use a single key instead: cache_depth: :depth_cach_column_name.
  cache_depth: true still defaults to ancestry_depth.

Breaking Changes

• siblings no longer returns self. This is a bug fix, but does change behavior.
• Dropped support for Rails < 6.1
• Renamed internal methods to follow Rails conventions: *_before_save methods renamed to *_before_last_save
  (e.g., child_ancestry_before_save => child_ancestry_before_last_save)
• Options are no longer set via class methods. Using has_ancestry is now the only way to enable these features.
  These are all not part of the public API.
  • These are now class level read only accessors
    • ancestry_base_class (introduced 1.1, removed by #​633)
    • ancestry_column (introduced 1.2, removed by #​633)
    • ancestry_delimiter (introduced 4.3.0, removed by #​633)
    • depth_cache_column (introduced 4.3.0, removed by #​654)
  • These no longer have any accessors
    • ancestry_format (introduced 4.3.0, removed by #​654)
    • orphan_strategy (introduced 1.1, removed by #​617)
    • ancestry_primary_key_format (introduced 4.3.0, removed by #​649)
    • touch_ancestors (introduced 2.1, removed by TODO)
• These are seen as internal and may go away:
  • apply_orphan_strategy Please use orphan_strategy: :none and a custom before_destory instead.

v4.2.0

Compare Source

• added strategy: materialized_path2 #​571
• Added tree_view method #​561 (thx @​bizcho)
• Fixed bug when errors would not undo callbacks #​566 (thx @​daniloisr)
• ruby 3.0 support
• rails 7.0 support (thx @​chenillen, @​petergoldstein)
• Documentation fixes (thx @​benkoshy, @​mijoharas)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[kbrock]

Curious why it tried to searialize a UserProvidedDefault (standard active record/active model value) to the database.

Sounds like the yaml serialization has a potential bug in here.
This happend for a while with automate request serialization and the queue. was a big mess trying to fix... so may want to take a peek here.

[miq-bot]

Checked commit 2e6bf2f with ruby 3.3.12, rubocop 1.89.0, haml-lint 0.78.0, and yamllint 1.37.1
1 file checked, 0 offenses detected
Everything looks fine. 🍪