Skip to content

[Task]: BC Breaks for new branch strategy in master branch#29

Open
robertSt7 wants to merge 1 commit into2026.xfrom
newbranch-strategy-bcbreak
Open

[Task]: BC Breaks for new branch strategy in master branch#29
robertSt7 wants to merge 1 commit into2026.xfrom
newbranch-strategy-bcbreak

Conversation

@robertSt7
Copy link

No description provided.

@robertSt7 robertSt7 added this to the 2026.1.0 milestone Feb 27, 2026
@robertSt7 robertSt7 self-assigned this Feb 27, 2026
@jdreesen
Copy link
Contributor

Where are the BC Breaks?

@jdreesen
Copy link
Contributor

jdreesen commented Mar 2, 2026

@kingjia90 Because it cannot comment on the other PR anymore:

Dropping PHP 8.3 alone should count as bc-break, right? But i maybe get what you are meaning, like, there is no code breaking, it's more an indirect requirement change

No, dropping support for a PHP version is not breaking, as composer just won't install it on systems with an unsupported PHP version.

@kingjia90
Copy link
Contributor

Ah ok, it's improper to call it bc break then, but let's keep it to highlight these "major" changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants