-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Backward incompatible changes reference reports #276
Update Backward incompatible changes reference reports #276
Conversation
517ff8c
to
f2e0c67
Compare
Added backward incompatible changes reference reports for 2.4.7-2.4.7-p1 versions delta.
f2e0c67
to
05297a9
Compare
https://tools.ietf.org/ links are temporarily unavailable due to maintenance work on the site. |
@jeff-matthews @chernenm what do we do with this one? Are these changes looking valid? Do we want to publish this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Historically, as far as I know we've never published BIC reference for security patches. We published some highlight info related to 2.4.3-p1 and 2.4.3-p2, but that was a special request.
@chernenm, is it necessary to publish BIC reference for all security patches?
There is no way that the changes from Adobe Commerce are correct, I don't have access to that codebase, but it would be extremely surprising if so many classes and interfaces and blocks and what have you, got removed in a small patch release version... If I have to guess, the wrong info generated might be related to this issue magento/magento2#38858 |
@hostep Looks like so. Thanks for the heads-up! |
2.4.7-2.4.7-p1 Backward incompatible changes reference docs.
Preview: https://commerce-docs.github.io/commerce-php/development/backward-incompatible-changes/reference/