Update dependency ancestry to "~>4.3.0"#23559
Open
renovate[bot] wants to merge 1 commit intomasterfrom
Open
Conversation
Member
|
@kbrock Can you take a look here? I'm surprised this fails the specs. |
8817fe1 to
da7d2ff
Compare
da7d2ff to
f36c20d
Compare
f36c20d to
79746ad
Compare
Member
|
kicking |
79746ad to
6386abb
Compare
6386abb to
12130aa
Compare
Member
|
Checked commit 12130aa with ruby 3.3.10, rubocop 1.56.3, haml-lint 0.69.0, and yamllint |
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
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"→"~>4.3.0"Release Notes
stefankroes/ancestry (ancestry)
v4.3.3Compare Source
v4.3.2Compare Source
v4.3.1Compare Source
v4.3.0Compare Source
update_strategy#588 (thx @victorfgs)Notable features
Default configuration values are provided for a few options:
update_strategy,ancestry_format, andprimary_key_format.These can be set in an initializer via
Ancestry.default_{ancestry_format} = valueA new
ancestry_formatof:materialized_path2formats the ancestry column with leading and trailing slashes.It shows promise to make the
ancestryfield more sql friendly.Both of these are better documented in the readme.
Breaking changes
ancestry_primary_key_formatis now specified or a single key not the whole regular expression.We used to accept
/\A[0-9]+(/[0-9]+)*or'[0-9]', but now we only accept'[0-9]'.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.