Skip to content

feat: drop twig 2 #513

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 3 commits into from
Closed

Conversation

gimler
Copy link
Contributor

@gimler gimler commented Oct 23, 2024

No description provided.

@gimler gimler force-pushed the feature/drop-twig-2 branch 3 times, most recently from ceb1dbc to 9aff264 Compare October 23, 2024 12:29
@@ -22,7 +22,7 @@
"php-translation/symfony-storage": "^2.1",
"php-translation/extractor": "^2.0",
"nyholm/nsa": "^1.1",
"twig/twig": "^2.14.4 || ^3.3",
"twig/twig": "^3.12",
Copy link
Member

@bocharsky-bw bocharsky-bw Oct 23, 2024

Choose a reason for hiding this comment

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

We just dropped v2, I think it would be cool to keep the min available version of v3 for a while, WDYT? Or do we use something new that is available since 3.12?

Copy link
Member

Choose a reason for hiding this comment

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

Seems that 3.12 mostly adds a lot of deprecations in preparation of 4.x: https://github.com/twigphp/Twig/blob/3.x/CHANGELOG#L71

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes the twig_callable was added with twig 3.12 twigphp/Twig@3156d80

So to fix the mass deprecations we must set the minimum to 3.12

@gimler gimler force-pushed the feature/drop-twig-2 branch 2 times, most recently from 9aff264 to 604ecd2 Compare October 23, 2024 19:23
@ZZromanZZ
Copy link

Friendly reminder. Is there anything else to be done?

Copy link
Member

@rvanlaak rvanlaak left a comment

Choose a reason for hiding this comment

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

Thanks!

@ZZromanZZ
Copy link

Can we expect merge and new version anytime soon? Thank you very much

@rvanlaak
Copy link
Member

@ZZromanZZ is this PR blocking you in some kind of way? Can't imagine how dropping support could do that.

@bocharsky-bw
Copy link
Member

Ideally, we need to fix tests to be sure nothing is broken with the changes. We can do it here or probably better to do it in a separate PR. Any volunteers for this? Merging and releasing with completely red tests is an unstable way.

As soon as we have green tests - I will be happy to merge and release.

@gimler gimler force-pushed the feature/drop-twig-2 branch from 604ecd2 to d5e60d8 Compare March 26, 2025 10:36
@gimler gimler force-pushed the feature/drop-twig-2 branch from d5e60d8 to 98088f9 Compare March 26, 2025 11:14
@gimler gimler force-pushed the feature/drop-twig-2 branch from 98088f9 to a70c38f Compare March 26, 2025 12:36
@bocharsky-bw
Copy link
Member

bocharsky-bw commented Mar 27, 2025

@gimler Can we close this now? I see it was dropped in #516

@gimler
Copy link
Contributor Author

gimler commented Mar 27, 2025

No i will rebase this. I Hope later today

@gimler gimler closed this Mar 27, 2025
@gimler gimler deleted the feature/drop-twig-2 branch March 27, 2025 18:37
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.

4 participants