Skip to content

Upgraded the application to Symfony 3.2-RC1 and Twig 1.28 #403

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

Closed
wants to merge 1 commit into from
Closed

Upgraded the application to Symfony 3.2-RC1 and Twig 1.28 #403

wants to merge 1 commit into from

Conversation

javiereguiluz
Copy link
Member

No description provided.

"twig/extensions" : "^1.3",
"twig/twig" : "^1.27",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really need to bump Twig version in composer.json? I mean, do we really have strict dependency with Twig v1.28? it would be enough composer up twig/twig - Composer will install 1.28 and freeze it in composer.lock anyway since we have ^ in composer.json.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes and no. As you can see in the CHANGELOG of 3.2-rc1:

bug #20484 bumped min version of Twig to 1.28 (@fabpot)

When some minimum version (e.g. 1.28) is mandatory for some dependency (e.g. Twig) I like to set it explicitly.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to know, thanks for the explanation!

@dzuelke
Copy link
Contributor

dzuelke commented Nov 28, 2016

Superseded by #405

@javiereguiluz
Copy link
Member Author

Closing it in favor of #405.

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.

3 participants