2.4.7-p1 incompatible with magento/module-b2b

[lohoy]

Preconditions and environment

Hello,

I have this issue with PHP 8.3 on Magento 2.4.7-p1.

Update: Error :

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - magento/module-b2b[100.4.0, ..., 100.4.1-p1] require php ~8.1.0||~8.2.0 -> your php version (8.3.6) does not satisfy that requirement.
    - magento/extension-b2b 1.4.2-p1 requires magento/module-b2b 100.4.1-p1 -> satisfiable by magento/module-b2b[100.4.1-p1].
    - Root composer.json requires magento/extension-b2b 1.4.2-p1 -> satisfiable by magento/extension-b2b[1.4.2-p1].

The modules B2B was not compatible with php8.3

This is same issue like 38858

Steps to reproduce

Use PHP 8.3.

composer require magento/extension-b2b:1.4.2-p1 -W

Expected result

Magento B2B works on PHP8.3

Actual result

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - magento/module-b2b[100.4.0, ..., 100.4.1-p1] require php ~8.1.0||~8.2.0 -> your php version (8.3.6) does not satisfy that requirement.
    - magento/extension-b2b 1.4.2-p1 requires magento/module-b2b 100.4.1-p1 -> satisfiable by magento/module-b2b[100.4.1-p1].
    - Root composer.json requires magento/extension-b2b 1.4.2-p1 -> satisfiable by magento/extension-b2b[1.4.2-p1].

Additional information

No response

Release note

No response

Triage and priority

• [X] 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”.

[m2-assistant[bot]]

Hi @lohoy. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Dash. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[engcom-Dash]

Hi @lohoy

Thanks for reporting and collaboration.

2.4.7-p1 b2b is not yet compatible with PHP 8.3.

Please refer to the below release notes:

https://experienceleague.adobe.com/en/docs/commerce-admin/b2b/release-notes#b2b-v142-p1

Thanks!

[lohoy]

Hello,

The warning was not on the release note the last week.

Do you have a date for the compatibility with PHP8.3? We upgrade server with PHP8.3 and it's very very important to us to know the date of the release.

Cordially

[engcom-Dash]

Hi @lohoy

We will update you on a date for the compatibility with PHP8.3.

Thanks!

[lohoy]

Hello,

I really need a fix because we change servers with our client and the upgrade was stopped due to this issue.

You don't have an estimation for the compatibility?

Have a good day.

[m2-assistant[bot]]

Hi @engcom-Delta. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.