Skip to content

Update sponsors for Symfony 7.3 #61016

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

Open
wants to merge 1 commit into
base: 7.3
Choose a base branch
from
Open

Conversation

mttsch
Copy link
Contributor

@mttsch mttsch commented Jul 1, 2025

Q A
Branch? 7.3
Bug fix? yes
New feature? no
Deprecations? no
Issues
License MIT

The sponsor is taken from https://symfony.com/blog/symfony-7-3-curated-new-features and https://symfony.com/releases/7.3.

@carsonbot
Copy link

Hey!

Thanks for your PR. You are targeting branch "7.4" but it seems your PR description refers to branch "7.3".
Could you update the PR description or change target branch? This helps core maintainers a lot.

Cheers!

Carsonbot

@mttsch mttsch changed the base branch from 7.4 to 7.3 July 1, 2025 15:56
Copy link
Contributor

@OskarStark OskarStark left a comment

Choose a reason for hiding this comment

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

But sulu and rector are still mentioned with their description in the next lines

@mttsch mttsch force-pushed the bugfix/sponsors branch from d3c1b68 to dc0b726 Compare July 1, 2025 18:07
@mttsch
Copy link
Contributor Author

mttsch commented Jul 1, 2025

@OskarStark Fixed. Using the same text as for 7.1 which is the same text as on the release pages except for replacing we with they.

automated refactoring, reduce maintenance costs, speed up feature delivery, and
transform legacy code into a strategic asset. They can handle the dirty work,
so you can focus on the features.
**Les-Tilleuls.coop** is a team of 70+ Symfony experts who can help you design, develop and
Copy link
Contributor

Choose a reason for hiding this comment

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

@dunglas @soyuka please approve

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants