Skip to content

Require the released quantum/framework 3.1 - #211

Merged
armanist merged 1 commit into
quantum-php:masterfrom
armanist:release/3.1.0-composer
Oct 24, 2026
Merged

armanist merged 1 commit into
quantum-php:masterfrom
armanist:release/3.1.0-composer

Conversation

@armanist

Copy link
Copy Markdown
Contributor

Requires the released framework instead of dev-master, now that quantum/framework 3.1.0 is tagged and on Packagist. Follows #210.

What changed

  • composer.json: quantum/framework is ^3.1 instead of dev-master.

Why

With dev-master, composer create-project and composer update pulled the latest, possibly unreleased, framework master. A project created from this release now gets the framework release it was prepared for.

Breaking changes

  • None for new projects. An existing project that wants to stay on the development branch can set the constraint back to dev-master in its own composer.json.

Testing

  • composer update --no-install in a clean copy resolves the whole dependency set and locks quantum/framework 3.1.0 from Packagist.
  • CI runs composer update, the checks and the API smoke test on PHP 8.1, 8.2 and 8.3.

Notes for reviewers

  • symfony/process and symfony/yaml are still pinned to the 5.4 line. Moving them is left for 3.1.1.

@quantum-php quantum-php deleted a comment from coderabbitai Bot Oct 24, 2026
@armanist
armanist merged commit bc98f73 into quantum-php:master Oct 24, 2026
5 checks passed
@armanist
armanist deleted the release/3.1.0-composer branch October 24, 2026 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant