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

How to restrict a symfony minor version for a project #31851

Closed
lyrixx opened this issue Jun 4, 2019 · 3 comments

Comments

Projects
None yet
3 participants
@lyrixx
Copy link
Member

commented Jun 4, 2019

Description

ATM, it's not possible to stick to a specific version of Symfony.
One of our application was using Symfony 4.2.*. With the release of Symfony 4.3.0 we get
some packages at 4.3.0. But there are some bugs (already fixed, but not released yet) that
prevent us to stay on 4.3.0

How to reproduce

composer create-project symfony/website-skeleton sf-42 '4.2.*'
cd sf-42
rm -rf vendor/ # This line is SUPER important
composer up
@stof

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

well, Flex has a way to do that. But if you run a composer update without Flex installed (because you deleted the vendor folder and you don't have it globally), Flex won't be able to restrict that as it won't run (it cannot run if it is not installed).

@nicolas-grekas

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

Closing as duplicate of symfony/flex#450, which is pending a PR ;)

@nicolas-grekas

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

Meanwhile: composer global require symfony/flex

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.