Bump craftcms/cms from 4.3.3 to 4.4.12

[dependabot]

Bumps craftcms/cms from 4.3.3 to 4.4.12.

Release notes

Sourced from craftcms/cms's releases.

4.4.12

• Asset indexes now remember their previously-selected source path. (#13147)
• Added the enabledForSite field for entries queried via GraphQL. (#13214)
• Added craft\base\ElementInterface::sourcePath().
• Improved craft\helpers\FileHelper::getExtensionByMimeType() for some ambiguous, web-friendly MIME types.
• Fixed a bug where reverting an entry’s content from a revision could omit some Matrix blocks.
• Fixed an error that could occur when adding a new site to an entry which contained Matrix blocks, if the same site had been added and removed previously.
• Fixed a bug where Matrix blocks nested within Neo or Super Table fields could be omitted when propagating an entry to a new site. (#13207)
• Fixed a bug where craft\web\View::registerTwigExtension() could throw an exception if Twig was already initialized. (#13208)
• Fixed a bug where entries mutated via GraphQL weren’t becoming globally enabled if enabled was set to true. (#13214)
• Fixed a styling issue with “Post Date” and “Expiry Date” fields. (#13216)
• Removed the OAuth 2.0 Client library, as it’s no longer used in core.
• Fixed a bug where activation emails sent to newly-created users could link to the front-end site, if they were granted control panel access via a user group. (#13204)
• Fixed a bug where “Required” lightswitch labels within field layout designers’ field settings slideouts weren’t getting translated. (#13230)
• Fixed a bug where Date fields could display the wrong date. (#13233)
• Deprecated the Craft.startsWith() JavaScript method. String.prototype.startsWith() should be used instead.
• Fixed two XSS vulnerabilities.

4.4.11

• Fixed a bug where Matrix blocks weren’t getting propagated to newly-added sites for entries. (#13181)
• Fixed a SQL error that could occur when updating to Craft 4.4 on PostgreSQL. (#13186)
• Fixed a bug where craft\helpers\StringHelper::isUtf8() was unreliable.
• Fixed a styling issue with Date fields. (#13182)

4.4.10.1

• Fixed a bug where it wasn’t possible to add new Matrix blocks via the “Add a block” menu. (#13177)

4.4.10

• PHP warnings and notices no longer halt execution when Dev Mode is disabled. (#13164)
• Fixed a “Double-instantiating a menu button on an element” console warning that occurred on pages with Matrix fields. (#6338)
• Fixed a bug where Quick Post widget settings weren’t filtering custom field options for the selected entry type.
• Fixed a bug where Matrix blocks could get detached from entries when sections were enabled for a new site. (#13155)
• Fixed an error that could occur when entrifying a global set without a field layout. (#13156)
• Fixed a bug where Single entries’ edit pages could have “Save and add another” actions. (#13157)
• Fixed styling issues with Date fields. (#13167)
• Fixed the vertical alignment of element labels. (#13168)
• Fixed a bug where the System Report utility could display MariaDB’s MySQL-equivalent version, if it was listed first in the server version string.
• Added craft\helpers\ArrayHelper::containsRecursive().
• craft\helpers\App::normalizeVersion() now returns the highest version found before distribution info.

4.4.9

• Volumes no longer validate if their field layout contains a field called extension, filename, height, kind, size, or width.
• It’s now possible for plugins to register errors to entries’ typeId, parentId, and authorId attributes. (#13138)
• Stack traces returned by craft\helpers\App::backtrace() now more closely resemble exception stack traces.
• “Element query executed before Craft is fully initialized” warnings now include a stack trace.
• Fixed a bug where queue-runner Ajax requests triggered on the front end weren’t getting closed before running the queue, potentially causing long front-end load delays.
• Fixed a bug where long element titles weren’t wrapping. (#13143)
• Fixed a user enumeration timing attack vulnerability.
• Fixed a SQL error that could occur when upgrading to Craft 4, if any matrixblocks table rows referenced nonexistent element IDs. (#13121)
• Fixed a SQL error that could occur when upgrading to Craft 4, if anything triggered an asset or volume query. (#13130)

... (truncated)

Changelog

Sourced from craftcms/cms's changelog.

4.4.12 - 2023-05-23

• Asset indexes now remember their previously-selected source path. (#13147)
• Added the enabledForSite field for entries queried via GraphQL. (#13214)
• Added craft\base\ElementInterface::sourcePath().
• Improved craft\helpers\FileHelper::getExtensionByMimeType() for some ambiguous, web-friendly MIME types.
• Fixed a bug where reverting an entry’s content from a revision could omit some Matrix blocks.
• Fixed an error that could occur when adding a new site to an entry which contained Matrix blocks, if the same site had been added and removed previously.
• Fixed a bug where Matrix blocks nested within Neo or Super Table fields could be omitted when propagating an entry to a new site. (#13207)
• Fixed a bug where craft\web\View::registerTwigExtension() could throw an exception if Twig was already initialized. (#13208)
• Fixed a bug where entries mutated via GraphQL weren’t becoming globally enabled if enabled was set to true. (#13214)
• Fixed a styling issue with “Post Date” and “Expiry Date” fields. (#13216)
• Removed the OAuth 2.0 Client library, as it’s no longer used in core.
• Fixed a bug where activation emails sent to newly-created users could link to the front-end site, if they were granted control panel access via a user group. (#13204)
• Fixed a bug where “Required” lightswitch labels within field layout designers’ field settings slideouts weren’t getting translated. (#13230)
• Fixed a bug where Date fields could display the wrong date. (#13233)
• Deprecated the Craft.startsWith() JavaScript method. String.prototype.startsWith() should be used instead.
• Fixed two XSS vulnerabilities.

4.4.11 - 2023-05-15

• Fixed a bug where Matrix blocks weren’t getting propagated to newly-added sites for entries. (#13181)
• Fixed a SQL error that could occur when updating to Craft 4.4 on PostgreSQL. (#13186)
• Fixed a bug where craft\helpers\StringHelper::isUtf8() was unreliable.
• Fixed a styling issue with Date fields. (#13182)

4.4.10.1 - 2023-05-10

• Fixed a bug where it wasn’t possible to add new Matrix blocks via the “Add a block” menu. (#13177)

4.4.10 - 2023-05-09

• PHP warnings and notices no longer halt execution when Dev Mode is disabled. (#13164)
• Fixed a “Double-instantiating a menu button on an element” console warning that occurred on pages with Matrix fields. (#6338)
• Fixed a bug where Quick Post widget settings weren’t filtering custom field options for the selected entry type.
• Fixed a bug where Matrix blocks could get detached from entries when sections were enabled for a new site. (#13155)
• Fixed an error that could occur when entrifying a global set without a field layout. (#13156)
• Fixed a bug where Single entries’ edit pages could have “Save and add another” actions. (#13157)
• Fixed styling issues with Date fields. (#13167)
• Fixed the vertical alignment of element labels. (#13168)
• Fixed a bug where the System Report utility could display MariaDB’s MySQL-equivalent version, if it was listed first in the server version string.
• Added craft\helpers\ArrayHelper::containsRecursive().
• craft\helpers\App::normalizeVersion() now returns the highest version found before distribution info.

4.4.9 - 2023-05-02

• Volumes no longer validate if their field layout contains a field called extension, filename, height, kind, size, or width.
• It’s now possible for plugins to register errors to entries’ typeId, parentId, and authorId attributes. (#13138)
• Stack traces returned by craft\helpers\App::backtrace() now more closely resemble exception stack traces.
• “Element query executed before Craft is fully initialized” warnings now include a stack trace.

... (truncated)

Commits

• 7a534f8 Merge branch 'release/4.4.12' into main
• cd8900b Finish 4.4.12
• 3fc3b9c Merge branch 'v3' of https://github.com/craftcms/cms into develop
• 1bb5d79 Finish 3.8.12
• cbb2dc9 Merge pull request #13235 from craftcms/t9n/develop
• 8f8f78c Merge pull request #13238 from craftcms/feature/source-path-keys--v4
• b1794fc Merge pull request #13237 from craftcms/feature/source-path-keys--v3
• 6a188a5 Merge branch 'feature/source-path-keys--v3' of https://github.com/craftcms/cm...
• f19a054 Release notes
• f9fe570 Fixed @since tags
• 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 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.