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

[dependabot]

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

Release notes

Sourced from craftcms/cms's releases.

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)
• Fixed a bug where the “Image Position” setting wasn’t saving for “Letterbox” image transforms. (#16648)
• Fixed a bug where the up command, the app/migrate action, and the Project Config utility weren’t aware of pending project config changes if a database backup was restored but caches weren’t cleared. (#16668)
• Fixed a bug where condition rules weren’t always getting created with their condition set. (#16676)
• Fixed an error that occurred when opening the filter HUD within the element selection modal for a relational field, if the user didn’t have permission to view the selected source outside of the field. (#16678)
• Fixed a bug where Number fields weren’t getting sorted properly in PostgreSQL. (#15828)
• Fixed a bug where Matrix fields’ “Default View Mode” settings included a “Display in a structured table” option. (#16631)
• Fixed a bug where user addresses weren’t getting restored when soft-deleted users were restored. (#16636)
• Fixed a bug where pressing the “New entry” button multiple times quickly would create multiple nested entries, circumventing the “Max Entries” settings. (#16642)
• Fixed a bug where Link fields without values were always getting marked as dirty when making another change to the element. (#16649)
• Fixed an error that could occur when programmatically duplicating a nested element for a new site. (#16659)
• Fixed a bug where Link fields’ “URL Suffix” and “Target” advanced fields were getting enabled even if they had been disabled in Craft 5.5. (#16663)
• Fixed an error that occurred when executing the users/remove-2fa command.
• Fixed a potential phishing attack vector.
• Fixed styling issues. (#16683, #16684)

5.6.5.1

• Fixed an error that could occur when saving elements with nested elements on multi-site installs. (#16609)

5.6.5

• Fixed a bug where transformed images could be slightly smaller than they should be when using the fit transform mode. (#16622)
• Fixed a bug where tests weren’t outputting exceptions thrown during Craft installation. (#16624)

... (truncated)

Changelog

Sourced from craftcms/cms's changelog.

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)

5.6.6 - 2025-02-11

• 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)
• Fixed a bug where the “Image Position” setting wasn’t saving for “Letterbox” image transforms. (#16648)
• Fixed a bug where the up command, the app/migrate action, and the Project Config utility weren’t aware of pending project config changes if a database backup was restored but caches weren’t cleared. (#16668)
• Fixed a bug where condition rules weren’t always getting created with their condition set. (#16676)
• Fixed an error that occurred when opening the filter HUD within the element selection modal for a relational field, if the user didn’t have permission to view the selected source outside of the field. (#16678)
• Fixed a bug where Number fields weren’t getting sorted properly in PostgreSQL. (#15828)
• Fixed a bug where Matrix fields’ “Default View Mode” settings included a “Display in a structured table” option. (#16631)
• Fixed a bug where user addresses weren’t getting restored when soft-deleted users were restored. (#16636)
• Fixed a bug where pressing the “New entry” button multiple times quickly would create multiple nested entries, circumventing the “Max Entries” settings. (#16642)
• Fixed a bug where Link fields without values were always getting marked as dirty when making another change to the element. (#16649)
• Fixed an error that could occur when programmatically duplicating a nested element for a new site. (#16659)
• Fixed a bug where Link fields’ “URL Suffix” and “Target” advanced fields were getting enabled even if they had been disabled in Craft 5.5. (#16663)
• Fixed an error that occurred when executing the users/remove-2fa command.
• Fixed a potential phishing attack vector.
• Fixed styling issues. (#16683, #16684)

5.6.5.1 - 2025-02-04

• Fixed an error that could occur when saving elements with nested elements on multi-site installs. (#16609)

... (truncated)

Commits

• d6e5866 Finish 5.6.8
• 5c368e0 Merge branch '4.x' of https://github.com/craftcms/cms into 5.x
• 90b16d9 Finish 4.14.7
• c7f5d32 Merge branch '4.x' of https://github.com/craftcms/cms into 5.x
• d698034 Only delete the old file if its location actually changed
• 27f9fdf Fixed Sort field bug
• 7a770d7 Merge branch 'JodebaDigitalPulse/5.x' into 5.x
• 925c247 Release note
• c7ee38e Cleanup + check getIsConsoleRequest()
• 8e65ba8 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 #63.