magento2: Can not install Magento 2.4.7-beta1 by composer

Preconditions and environment

• Magento v2.4.7-beta1
• Composer v2.5.8

Steps to reproduce

Install Magento 2.4.7-beta1 by composer: composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition=2.4.7-beta1 magento

Expected result

Install process without error

Actual result

composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition=2.4.7-beta1 magento
Creating a "magento/project-community-edition=2.4.7-beta1" project at "magento/"
Installing magento/project-community-edition (2.4.7-beta1)
  - Downloading magento/project-community-edition (2.4.7-beta1)
  - Installing magento/project-community-edition (2.4.7-beta1): Extracting archive
Created project in /home/magento/
Loading composer repositories with package information
Info from https://repo.packagist.org: #StandWithUkraine
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - paypal/module-braintree 4.6.0-beta1 requires paypal/module-braintree-customer-balance 4.6.0-beta1 -> could not be found in any version, there may be a typo in the package name.
    - magento/product-community-edition 2.4.7-beta1 requires adobe-commerce/os-extensions-metapackage ~1.0 -> satisfiable by adobe-commerce/os-extensions-metapackage[1.0.0-beta1].
    - adobe-commerce/os-extensions-metapackage 1.0.0-beta1 requires paypal/module-braintree ~4.6.0 -> satisfiable by paypal/module-braintree[4.6.0-beta1].
    - Root composer.json requires magento/product-community-edition 2.4.7-beta1 -> satisfiable by magento/product-community-edition[2.4.7-beta1].

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.