[6.x] Potential Composer conflict on "doctrine/dbal ^4.0@RC"

[caseydwyer]

Description

Realize 6.x is extremely hot off the press, here (congrats, btw!) so if I need to just pump the brakes, let me know. 🙂 When trying to upgrade, however, we get this:

statamic-rad-pack/runway v6.0.0 requires doctrine/dbal ^4.0@RC -> found doctrine/dbal[4.0.0-beta1, ..., 4.0.x-dev] but it does not match your minimum-stability.

Any thoughts on that?

Steps to reproduce

Attempt to upgrade from 5.x via composer update command.

Environment

Environment

Environment Application Name: TF Laravel Version: 10.40.0 PHP Version: 8.2.5 Composer Version: 2.5.4 Environment: local Debug Mode: ENABLED URL: tf.test Maintenance Mode: OFF Cache Config: NOT CACHED Events: NOT CACHED Routes: NOT CACHED Views: NOT CACHED Drivers Broadcasting: log Cache: statamic Database: mysql Logs: stack / single Mail: smtp Queue: sync Session: file Livewire Livewire: v3.3.5 Statamic Addons: 6 Antlers: runtime Stache Watcher: Enabled Static Caching: Disabled Version: 4.44.0 PRO Statamic Addons doefom/currency-fieldtype: dev-main eminos/statamic-group: 2.0.1 eminos/statamic-tabs: 1.1.0 jacksleight/statamic-miniset: 1.0.2 statamic-rad-pack/runway: 5.6.1 statamic/eloquent-driver: 2.10.0 Statamic Eloquent Driver Asset Containers: file Assets: file Blueprints: file Collection Trees: file Collections: file Entries: eloquent Forms: file Global Sets: file Global Variables: file Navigation Trees: file Navigations: file Revisions: eloquent Taxonomies: file Terms: file

[duncanmcclean]

Thanks - I got that too a few minutes ago. Will see what I can do.

[duncanmcclean]

Should be fixed by ef32e01cc12a16d1452c599c5071e86ccfef679c.

[duncanmcclean]

v6.0.1 should sort out the doctrine/dbal issue.