Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump craftcms/cms from 5.0.0-beta.10 to 5.5.10 #53

Open
wants to merge 1 commit into
base: develop-v5
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jan 15, 2025

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

Release notes

Sourced from craftcms/cms's releases.

5.5.10

  • Fixed a bug where the control panel could display a notice about the Craft CMS license belonging to a different domain, even when accessing the control panel from the correct domain. (#16396)
  • Fixed a bug where Unicode special characters weren’t getting stripped out of search keywords. (#16430)
  • Fixed an error that could occur when setting relatedTo* GraphQL arguments to null. (#16431)
  • Fixed a bug where field layout elements’ action menus could have an empty action group.
  • Fixed a bug where Single section entries could be duplicated after running the entry-types/merge command. (#16394)
  • Fixed a styling bug with the system message modal. (#16410)
  • Fixed a bug where relational fields could eager-load elements from a different instance of the same field, if one of the instances had no relations. (#16191)
  • Fixed a bug where the utils/prune-revisions command was deleting nested entry revisions.

5.5.9

  • Fixed a bug where custom fields could cause validation errors when running the users/create command.
  • Fixed a bug where deleting a volume folder wasn’t fully deleting asset data in descendant folders.
  • Fixed a bug where ancestors, children, descendants, and parent eager-loading wasn’t working on some environments. (#16381, #16382)
  • Fixed a JavaScript error that could occur if there was a problem applying changes to field layout elements. (#16380)
  • Fixed a bug where field layout designers were validating field names, handles, and instructions, even if they weren’t overridden within the field instance. (#16380)
  • Fixed an error that occurred when upgrading to Craft 5. (#16383)
  • Fixed a bug where “Full Name” could appear twice in the user card attributes list. (#16358)
  • Fixed a bug where multi-site element queries could return an incorrect number of results if the search param was used in conjunction with offset or limit. (#16183)

5.5.8

  • Fixed a bug where custom fields were getting included in rendered field layout forms, even if their getInputHtml() method returned an empty string.
  • Fixed a bug where the password input on the Set Password page wasn’t including the “Show” button.
  • Fixed a SQL error that could occur if an element was saved with a title longer than 255 characters.
  • Fixed a bug where some UI messages began with a lowercase letter in some languages. (#16354)
  • Fixed errors that could occur when working with field layouts for element types that are no longer installed. (#16352)
  • Fixed an error that could occur when creating nested entries within Matrix fields. (#16331)
  • Fixed a bug where element index View menus could include a “Use defaults” button when no view customizations had been made.
  • Fixed a bug where new entries’ slugs weren’t getting propagated to other sites, if their entry type had a dynamic title format. (#16347)
  • Fixed a bug where address cards were only showing the first two lines of the address. (#16353)
  • Fixed a bug where @transform GraphQL directives weren’t always working on Assets fields with overridden handles. (#15718)
  • Fixed an error that occurred when adding “Full Name” to user cards. (#16358)
  • Fixed an error that could occur if craft\base\NestedElementTrait::getOwner() or getPrimaryOwner() were called on a nested element whose owner didn’t exist in the same site. (#16359)
  • Fixed a styling issue. (#16342)
  • Fixed an RCE vulnerability.

5.5.7

  • Fixed a bug where elements’ getPrev() and getNext() methods could cause duplicate queries. (#16329)
  • Fixed a bug where assets that were shorter than the preview thumb container weren’t getting vertically centered within it.
  • Fixed a bug where it was possible to set a focal point on SVGs, even though focal points on SVGs aren’t supported. (#16258)
  • Fixed a bug where ancestors, children, descendants, and parent eager-loading wasn’t working for previewed elements. (#16327)
  • Fixed a bug where field conditions weren’t taking effect within Matrix fields set to inline-editable blocks mode, if the owner element didn’t support drafts. (#16315)
  • Fixed a bug where Matrix fields’ entry types weren’t maintaining their original block type order when upgrading to Craft 5. (#16314)
  • Fixed a bug where element card labels were getting cut off when wrapped. (#16325)
  • Fixed a PHP error that could occur when eager-loading owner or primaryOwner on nested elements. (#16339)

5.5.6.1

  • Fixed a bug where Tags fields had “Replace” actions. (#16310)
  • Fixed styling issues. (#16298, #16312)

... (truncated)

Changelog

Sourced from craftcms/cms's changelog.

5.5.10 - 2025-01-14

  • Fixed a bug where the control panel could display a notice about the Craft CMS license belonging to a different domain, even when accessing the control panel from the correct domain. (#16396)
  • Fixed a bug where Unicode special characters weren’t getting stripped out of search keywords. (#16430)
  • Fixed an error that could occur when setting relatedTo* GraphQL arguments to null. (#16431)
  • Fixed a bug where field layout elements’ action menus could have an empty action group.
  • Fixed a bug where Single section entries could be duplicated after running the entry-types/merge command. (#16394)
  • Fixed a styling bug with the system message modal. (#16410)
  • Fixed a bug where relational fields could eager-load elements from a different instance of the same field, if one of the instances had no relations. (#16191)
  • Fixed a bug where the utils/prune-revisions command was deleting nested entry revisions.

5.5.9 - 2025-01-06

  • Fixed a bug where custom fields could cause validation errors when running the users/create command.
  • Fixed a bug where deleting a volume folder wasn’t fully deleting asset data in descendant folders.
  • Fixed a bug where ancestors, children, descendants, and parent eager-loading wasn’t working on some environments. (#16381, #16382)
  • Fixed a JavaScript error that could occur if there was a problem applying changes to field layout elements. (#16380)
  • Fixed a bug where field layout designers were validating field names, handles, and instructions, even if they weren’t overridden within the field instance. (#16380)
  • Fixed an error that occurred when upgrading to Craft 5. (#16383)
  • Fixed a bug where “Full Name” could appear twice in the user card attributes list. (#16358)
  • Fixed a bug where multi-site element queries could return an incorrect number of results if the search param was used in conjunction with offset or limit. (#16183)

5.5.8 - 2025-01-02

  • Fixed a bug where custom fields were getting included in rendered field layout forms, even if their getInputHtml() method returned an empty string.
  • Fixed a bug where the password input on the Set Password page wasn’t including the “Show” button.
  • Fixed a SQL error that could occur if an element was saved with a title longer than 255 characters.
  • Fixed a bug where some UI messages began with a lowercase letter in some languages. (#16354)
  • Fixed errors that could occur when working with field layouts for element types that are no longer installed. (#16352)
  • Fixed an error that could occur when creating nested entries within Matrix fields. (#16331)
  • Fixed a bug where element index View menus could include a “Use defaults” button when no view customizations had been made.
  • Fixed a bug where new entries’ slugs weren’t getting propagated to other sites, if their entry type had a dynamic title format. (#16347)
  • Fixed a bug where address cards were only showing the first two lines of the address. (#16353)
  • Fixed a bug where @transform GraphQL directives weren’t always working on Assets fields with overridden handles. (#15718)
  • Fixed an error that occurred when adding “Full Name” to user cards. (#16358)
  • Fixed an error that could occur if craft\base\NestedElementTrait::getOwner() or getPrimaryOwner() were called on a nested element whose owner didn’t exist in the same site. (#16359)
  • Fixed a styling issue. (#16342)
  • Fixed an RCE vulnerability.

5.5.7 - 2024-12-17

  • Fixed a bug where elements’ getPrev() and getNext() methods could cause duplicate queries. (#16329)
  • Fixed a bug where assets that were shorter than the preview thumb container weren’t getting vertically centered within it.
  • Fixed a bug where it was possible to set a focal point on SVGs, even though focal points on SVGs aren’t supported. (#16258)
  • Fixed a bug where ancestors, children, descendants, and parent eager-loading wasn’t working for previewed elements. (#16327)
  • Fixed a bug where field conditions weren’t taking effect within Matrix fields set to inline-editable blocks mode, if the owner element didn’t support drafts. (#16315)
  • Fixed a bug where Matrix fields’ entry types weren’t maintaining their original block type order when upgrading to Craft 5. (#16314)
  • Fixed a bug where element card labels were getting cut off when wrapped. (#16325)
  • Fixed a PHP error that could occur when eager-loading owner or primaryOwner on nested elements. (#16339)

... (truncated)

Commits

Dependabot compatibility score

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)

Bumps [craftcms/cms](https://github.com/craftcms/cms) from 5.0.0-beta.10 to 5.5.10.
- [Release notes](https://github.com/craftcms/cms/releases)
- [Changelog](https://github.com/craftcms/cms/blob/5.x/CHANGELOG.md)
- [Commits](craftcms/cms@5.0.0-beta.10...5.5.10)

---
updated-dependencies:
- dependency-name: craftcms/cms
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants