Skip to content
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

Inform about potential BC break after response code change #495

Merged
merged 1 commit into from
Oct 31, 2022

Conversation

Zales0123
Copy link
Member

Q A
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Related tickets
License MIT

Btw, nothing changed in the UPGRADE file since 1.7 release 😅 we should probably take care of documenting some changes between 1.7, 1.8, 1.9 and 1.10 💃

@Zales0123 Zales0123 added the Maintenance Configurations, READMEs, releases, etc. label Oct 31, 2022
@Zales0123 Zales0123 requested a review from a team as a code owner October 31, 2022 09:22
@Zales0123 Zales0123 merged commit 4ac8fef into Sylius:1.10 Oct 31, 2022
@Zales0123 Zales0123 deleted the inform-about-potential-bc-break branch October 31, 2022 09:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Configurations, READMEs, releases, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants