Open
Conversation
Member
| Checked commit b4eda2b with ruby 3.3.10, rubocop 1.56.3, haml-lint 0.72.0, and yamllint 1.37.1 |
Member
| Curious why it tried to searialize a Sounds like the yaml serialization has a potential bug in here. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
"~>4.1.0"→"~>5.1.0"Release Notes
stefankroes/ancestry (ancestry)
v5.1.0Compare Source
update_strategy: :sqlnow works on all databases (SQLite, MySQL, PostgreSQL) #715Deprecations
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_ancestorsBreaking Changes
sort_by_ancestryandcheck_ancestry_integrity!now delegate to_sort_by_ancestryand_check_ancestry_integrity!with an explicit column parameter. The public API is unchanged.v5.0.0Compare Source
siblingsnow excludes self #710 (thx @chikamichi)orphan_strategy: :none#658rebuild_counter_cache!to reset counter caches. #663 #668 (thx @RongRongTeng)in_subtree_of?instance method #680 (thx @instrumentl)has_siblings?to useexists?#693 (thx @a5-stable)update_strategy: :sqlhooks for extension developersbuild_cache_depth_sql!, a sql alternative tobuild_cache_depth#654ancestry_primary_key_format#649Notable features
Depth scopes now work without
cache_depth. But please only use this in backgroundjobs. If you need to do this in the ui, please use
cache_depth.build_cache_depth_sql!is quicker thanbuild_cache_depth!(1 query instead of N+1 queries).Deprecations
:depth_cache_columnis going away.Please use a single key instead:
cache_depth: :depth_cach_column_name.cache_depth: truestill defaults toancestry_depth.Breaking Changes
siblingsno longer returns self. This is a bug fix, but does change behavior.*_before_savemethods renamed to*_before_last_save(e.g.,
child_ancestry_before_save=>child_ancestry_before_last_save)has_ancestryis now the only way to enable these features.These are all not part of the public API.
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)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)apply_orphan_strategyPlease useorphan_strategy: :noneand a custombefore_destoryinstead.v4.3.3Compare Source
v4.3.2Compare Source
v4.3.1Compare Source
v4.3.0Compare Source
siblingsnow excludes self #710 (thx @chikamichi)orphan_strategy: :none#658rebuild_counter_cache!to reset counter caches. #663 #668 (thx @RongRongTeng)in_subtree_of?instance method #680 (thx @instrumentl)has_siblings?to useexists?#693 (thx @a5-stable)update_strategy: :sqlhooks for extension developersbuild_cache_depth_sql!, a sql alternative tobuild_cache_depth#654ancestry_primary_key_format#649Notable features
Depth scopes now work without
cache_depth. But please only use this in backgroundjobs. If you need to do this in the ui, please use
cache_depth.build_cache_depth_sql!is quicker thanbuild_cache_depth!(1 query instead of N+1 queries).Deprecations
:depth_cache_columnis going away.Please use a single key instead:
cache_depth: :depth_cach_column_name.cache_depth: truestill defaults toancestry_depth.Breaking Changes
siblingsno longer returns self. This is a bug fix, but does change behavior.*_before_savemethods renamed to*_before_last_save(e.g.,
child_ancestry_before_save=>child_ancestry_before_last_save)has_ancestryis now the only way to enable these features.These are all not part of the public API.
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)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)apply_orphan_strategyPlease useorphan_strategy: :noneand a custombefore_destoryinstead.v4.2.0Compare Source
Configuration
📅 Schedule: 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.
This PR was generated by Mend Renovate. View the repository job log.