Bump craftcms/cms from 5.0.0-beta.10 to 5.6.10.1

[dependabot]

Bumps craftcms/cms from 5.0.0-beta.10 to 5.6.10.1.

Release notes

Sourced from craftcms/cms's releases.

5.6.10.1

• Fixed a bug where field layout designers’ library HUDs weren’t scrollable.

5.6.10

• Added craft\base\ElementTrait::$isNewSite.
• Added craft\queue\jobs\PropagateElements::$isNewSite.
• Field layout designers’ library HUDs are now limited to 600 pixels high. (#16772)
• Fixed an error that could occur when saving elements, if any dependencies defined global functions whose names conflicted with Yii’s built-in validator names, such as string().
• Fixed a bug where ancestors and parent eager-loading wasn’t working on some environments. (#16381, #16382, #16341)
• Fixed a bug where asset, category, and tag relations weren’t propagating to newly-created sites for global sets. (#16752)
• Fixed a bug where database backups weren’t always using the correct charset. (#16753)
• Fixed styling issues. (#16755, #16756, #16760, #16748, #16770)

5.6.9.1

• Fixed a bug where newly-created custom fields wouldn’t have their full settings intact for afterSave().

5.6.9

• Fixed a bug where scrollable panes weren’t automatically scrolling when dragging objects near their edges. (#16738)
• Fixed a bug where “Applying new propagation method to [Field Name] entries” jobs weren’t getting queued when deploying changes to Matrix fields’ Propagation Method settings. (#16740)
• Fixed a bug where field layout designers’ library HUDs could open above the “Add” button, hiding the tab contents. (#16747)

5.6.8

• Added craft\base\Element::ancestors().
• Added craft\base\Element::descendants().
• Fixed an error that occurred when deleting a category or Structure section entry if its ancestors were eager-loaded. (#16722)
• Fixed a bug where category and entry edit pages didn’t include breadcrumbs for any disabled ancestor elements.
• Fixed a bug where the “Delete (with descendants)” bulk element action wasn’t deleting disabled descendants.
• Fixed a bug where asset files could be deleted when modified. (#16686)
• Fixed an error that could occur if a Matrix field was saved from a console request. (#16724)
• Fixed a bug where the Sort field within element index View menus wasn’t updating after the sort attribute/direction was changed by pressing on a table header.

5.6.7

• Fixed a bug where multiple “New file uploaded.” notifications could be shown at once. (#16688)
• Fixed an error that could occur during garbage collection if the database user didn’t have permission to disable foreign key constraints. (#16700)
• Fixed a bug where datepickers could have scrollbars. (#16697)
• Fixed a bug where asset files could be prematurely deleted when moved to a different volume, if an error occurred. (#16686)
• Fixed a bug where clearing out a Structure section’s Parent field wasn’t persisting if editing the entry for a newly-added site. (#16691)
• Fixed a bug where SVG asset transforms could get two preserveAspectRatio attributes. (#16709)
• Fixed a bug where Number fields weren’t handling semi-numeric strings properly. (craftcms/feed-me#1575)
• Fixed an error that could occur if a field’s input HTML contained <style> tags. (nystudio107/craft-retour#329)
• Fixed a bug where slideouts weren’t fully initializing/deinitializing their UI for users who preferred reduced motion. (#16707)
• Fixed a bug where GraphQL types for entry types were being named using sections’ and fields’ handle overrides. (#16713)
• Fixed styling issues. (#16699, #16712, #16721)

5.6.6

• Fixed a bug where multi-site elements’ search indexes could be updated twice.
• Fixed a bug where some nested Matrix entries weren’t getting propagated to newly-added sites of their owners, if any blocks had been modified. (#16640)
• Fixed an error that could occur when deleting a draft.
• Fixed an error that could occur when saving a Structure section entry, if it had an Assets field with a dynamic subpath that referenced level. (#16661)
• Fixed a bug where “Fit” image transforms were showing the “Default Focal Point” setting. (#16665)

... (truncated)

Changelog

Sourced from craftcms/cms's changelog.

5.6.10.1 - 2025-02-25

• Fixed a bug where field layout designers’ library HUDs weren’t scrollable.

5.6.10 - 2025-02-25

• Added craft\base\ElementTrait::$isNewSite.
• Added craft\queue\jobs\PropagateElements::$isNewSite.
• Field layout designers’ library HUDs are now limited to 600 pixels high. (#16772)
• Fixed an error that could occur when saving elements, if any dependencies defined global functions whose names conflicted with Yii’s built-in validator names, such as string().
• Fixed a bug where ancestors and parent eager-loading wasn’t working on some environments. (#16381, #16382, #16341)
• Fixed a bug where asset, category, and tag relations weren’t propagating to newly-created sites for global sets. (#16752)
• Fixed a bug where database backups weren’t always using the correct charset. (#16753)
• Fixed styling issues. (#16755, #16756, #16760, #16748, #16770)

5.6.9.1 - 2025-02-20

• Fixed a bug where newly-created custom fields wouldn’t have their full settings intact for afterSave().

5.6.9 - 2025-02-20

• Fixed a bug where scrollable panes weren’t automatically scrolling when dragging objects near their edges. (#16738)
• Fixed a bug where “Applying new propagation method to [Field Name] entries” jobs weren’t getting queued when deploying changes to Matrix fields’ Propagation Method settings. (#16740)
• Fixed a bug where field layout designers’ library HUDs could open above the “Add” button, hiding the tab contents. (#16747)

5.6.8 - 2025-02-19

• Added craft\base\Element::ancestors().
• Added craft\base\Element::descendants().
• Fixed an error that occurred when deleting a category or Structure section entry if its ancestors were eager-loaded. (#16722)
• Fixed a bug where category and entry edit pages didn’t include breadcrumbs for any disabled ancestor elements.
• Fixed a bug where the “Delete (with descendants)” bulk element action wasn’t deleting disabled descendants.
• Fixed a bug where asset files could be deleted when modified. (#16686)
• Fixed an error that could occur if a Matrix field was saved from a console request. (#16724)
• Fixed a bug where the Sort field within element index View menus wasn’t updating after the sort attribute/direction was changed by pressing on a table header.

5.6.7 - 2025-02-18

• Fixed a bug where multiple “New file uploaded.” notifications could be shown at once. (#16688)
• Fixed an error that could occur during garbage collection if the database user didn’t have permission to disable foreign key constraints. (#16700)
• Fixed a bug where datepickers could have scrollbars. (#16697)
• Fixed a bug where asset files could be prematurely deleted when moved to a different volume, if an error occurred. (#16686)
• Fixed a bug where clearing out a Structure section’s Parent field wasn’t persisting if editing the entry for a newly-added site. (#16691)
• Fixed a bug where SVG asset transforms could get two preserveAspectRatio attributes. (#16709)
• Fixed a bug where Number fields weren’t handling semi-numeric strings properly. (craftcms/feed-me#1575)
• Fixed an error that could occur if a field’s input HTML contained <style> tags. (nystudio107/craft-retour#329)
• Fixed a bug where slideouts weren’t fully initializing/deinitializing their UI for users who preferred reduced motion. (#16707)
• Fixed a bug where GraphQL types for entry types were being named using sections’ and fields’ handle overrides. (#16713)
• Fixed styling issues. (#16699, #16712, #16721)

... (truncated)

Commits

• 6593979 5.6.10.1 - fix scroll bug
• c9f1527 Finish 5.6.10
• 838eef3 Merge branch '4.x' of https://github.com/craftcms/cms into 5.x
• 67ba094 Finish 4.14.9
• b297e0f Limit FLD height
• 1ca199a Merge pull request #16770 from craftcms/feature/pt-2495-the-actions-button-is...
• a17d891 Release note
• 3a1dd20 Merge branch '5.x' into feature/pt-2495-the-actions-button-is-missing-a-focus...
• fc29bdb Update @since tags
• dd3db10 Merge branch '4.x' of https://github.com/craftcms/cms into 5.x
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #66.