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

[robertSt7]

No description provided.

[jdreesen]

Where are the BC Breaks?

[jdreesen]

@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]

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

[Copilot]

Pull request overview

Updates the bundle generator to align with Pimcore’s new (2026.x) branch/versioning strategy and removes Admin Classic-specific bundle scaffolding.

Changes:

• Update composer.json to require pimcore/pimcore ^2026.1 and add a branch-alias for dev-2026.x.
• Simplify the generated bundle class template by removing PimcoreBundleAdminClassicInterface, BundleAdminClassicTrait, and related methods.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
src/Resources/skeleton/bundle/Bundle.php.twig	Removes Admin Classic interface/trait and JS path registration from generated bundle classes.
composer.json	Bumps Pimcore dependency to the 2026.1 line and adds branch alias metadata.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.