Bump cakephp/migrations from 4.1.1 to 4.4.0

[dependabot]

Bumps cakephp/migrations from 4.1.1 to 4.4.0.

Release notes

Sourced from cakephp/migrations's releases.

CakePHP Migrations 4.4.0

Default backend update

Following the addition of the builtin backend in 4.3.0, the builtin backend is now the default in 4.4.0. If your migrations don't run correctly with 4.4.0 please open an issue. You can temporarily switch back to the phinx backend by setting Migrations.backend = 'phinx' in your config/app.php.

The phinx backend is planned for removal in the 5.0 release which will follow 4.4 after collecting feedback from the community for a few months.

What's Changed

• Start update for php 8.4 by @​markstory in cakephp/migrations#729
• Use actual Migrations version in builtin backend doc by @​MasterOdin in cakephp/migrations#733
• update stan by @​LordSimal in cakephp/migrations#734
• 4.next: add PHPUnit 11 support by @​LordSimal in cakephp/migrations#736
• Make builtin the default migrations backend by @​markstory in cakephp/migrations#738

Full Changelog: cakephp/migrations@4.3.2...4.4.0

CakePHP Migrations 4.3.2

What's Changed

• Add datetime column support to addTimestamps() by @​markstory in cakephp/migrations#721
• Check for potentially undefined command line argument by @​markstory in cakephp/migrations#726
• Add getDecoratedConnection to 4.x by @​markstory in cakephp/migrations#732

Full Changelog: cakephp/migrations@4.3.1...4.3.2

CakePHP Migrations 4.3.1

What's Changed

• Handle database with escapable identifiers in name by @​jharder in cakephp/migrations#717
• Include the current backend in the entry point output by @​markstory in cakephp/migrations#718

New Contributors

• @​jharder made their first contribution in cakephp/migrations#717

Full Changelog: cakephp/migrations@4.3.0...4.3.1

CakePHP Migrations 4.3.0

New Backend

As of migrations 4.3. there is a new migrations backend that uses CakePHP's database abstractions and ORM. Longer term this will allow for phinx to be removed as a dependency. Reducing the dependencies of migrations helps keep your applications dependencies smaller. Migrations can also benefit from improvements in the ORM with less lag time as they no longer need to be re-implemented in phinx. Lastly, it streamlines the number of APIs you have to learn. Migrations included APIs that are very different from CakePHPs, and we can now align querying and data manipulation APIs so that you don't have to remember two different APIs depending on the context.

What is the same?

Your migrations shouldn't have to change much to adapt to the new backend. The migrations backend implements all of the phinx interfaces and can run migrations based on phinx classes. If your migrations fail for a reason not outlined below please open an issue.

What is different?

... (truncated)

Commits

• 6047ee0 Merge pull request #738 from cakephp/builtin-default
• dc6edfc Make builtin the default migrations backend
• c810685 Merge branch '4.x' into 4.next
• 9440f8d Merge pull request #736 from cakephp/4.next-phpunit11
• f5ff518 add phpunit 11 support - fix psalm
• d9ef1ad add phpunit 11 support - fix mysql tests
• 71ab060 add phpunit 11 support - fix psalm
• e59eaeb add phpunit 11 support - fix CS
• e0f8dbf add phpunit 11 support - part 4
• 6b6878c add phpunit 11 support - part 3
• 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 #32.