This PR was merged into the 2.7 branch.
Discussion
----------
[HttpKernel] Revert BC breaking change of Request::isMethodSafe()
| Q | A
| ------------- | ---
| Branch? | 2.7
| Bug fix? | yes
| New feature? | no
| BC breaks? | yes (reverting a previous BC break)
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #20562
| License | MIT
| Doc PR | -
As spotted in #20562, we should not have broken a minor version. Instead, we should have deprecated the bad behavior. This is done in #20603.
Commits
-------
0c3b7d7 [HttpKernel] Revert BC breaking change of Request::isMethodSafe()
This PR was merged into the 2.7 branch.
Discussion
----------
[DI] minor FileLoaders tests update
| Q | A
| ------------- | ---
| Branch? | 2.7
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | N/A
| License | MIT
| Doc PR | N/A
Strictly speaking not a bug fix but can be merged to 2.7 safely.
I don't know what was the idea behind this or if it simply was a mistake, but right now it seems weird 😅
Commits
-------
412fbe6 [DI] minor FileLoaders tests update
This PR was submitted for the master branch but it was merged into the 3.1 branch instead (closes#20613).
Discussion
----------
[Filesystem] Remove extra argv from dumpFile() calls in tests
| Q | A
| ------------- | ---
| Branch? | master
| Tests pass? | yes
| License | MIT
Commits
-------
1b298e5 [Filesystem] Remove extra argv in dumpFile() tests
This PR was merged into the 3.2 branch.
Discussion
----------
[FrameworkBundle] Add framework.cache.prefix_seed for predictible cache key prefixes
| Q | A
| ------------- | ---
| Branch? | 3.2
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | -
| License | MIT
| Doc PR | -
That's a design issue: using root_dir as discriminant doesn't work with blue/green deployment strategies, and doesn't prevent collision when different apps are deployed in the same path while sharing the same cache backend.
Commits
-------
82952bd [FrameworkBundle] Add framework.cache.prefix_seed for predictible cache key prefixes
This PR was merged into the 3.2 branch.
Discussion
----------
[WebProfilerBundle] Fix deprecated uses of profiler_dump
| Q | A
| ------------- | ---
| Branch? | 3.2
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | -
| License | MIT
| Doc PR | -
Replaces #20571 that made me realize that we completely missed updating the "Request / Response" panel that is current triggering a bunch of deprecation notices about profiler_dump. Yet, these notices triggered by the profiler are not displayed anywhere (what, we don't have a profiler for the profiler? :) ). And we missed them.
Commits
-------
b4c327d [WebProfilerBundle] Fix deprecated uses of profiler_dump
This PR was squashed before being merged into the 3.2 branch (closes#20590).
Discussion
----------
[DI] Allow null as default env value
| Q | A
| ------------- | ---
| Branch? | 3.2
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | ø
| License | MIT
| Doc PR | ø
This PR allows the environment variable default value to be null. The way, we can allow optional environment variables, such as in this example:
```yaml
parameters:
# Default values
env(DATABASE_HOST): database
env(DATABASE_PORT): ~
env(DATABASE_NAME): symfony
env(DATABASE_USERNAME): root
env(DATABASE_PASSWORD): ~
# Database configuration
database_host: "%env(DATABASE_HOST)%"
database_port: "%env(DATABASE_PORT)%"
database_name: "%env(DATABASE_NAME)%"
database_user: "%env(DATABASE_USERNAME)%"
database_password: "%env(DATABASE_PASSWORD)%"
```
Commits
-------
519a471 [DI] Allow null as default env value
This PR was merged into the 2.7 branch.
Discussion
----------
[Doctrine][Form] support large integers
| Q | A
| ------------- | ---
| Branch? | 2.7
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #15642
| License | MIT
| Doc PR | n/a
Commits
-------
6954a07 [Doctrine][Form] support large integers
This PR was submitted for the master branch but it was merged into the 3.2 branch instead (closes#20559).
Discussion
----------
[FrameworkBundle] Avoid warming up the validator cache for non-existent class
| Q | A
| ------------- | ---
| Branch? | master
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? |no
| Tests pass? | yes
| License | MIT
This relates to https://github.com/FriendsOfSymfony/FOSUserBundle/issues/2224 - where basically the cache warmer triggers autoloading of a class that is broken, and it then blows up.
This doesn't fix the problem in itself, loading broken classes will still fail, but it allows us at least to work around it by doing:
```
"exclude-from-classmap": [
"vendor/friendsofsymfony/user-bundle/Propel/"
]
```
And then `composer dump-autoload -a` to get an authoritative classmap. That way the hasMetadataFor will return false because class_exist() won't try to load the class at all. Without the hasMetadataFor fix though, it calls getMetadataFor which throws an exception in the case the class doesn't exist. I am not sure if that's by design.. that the cache warmer would force you to have classes existing for all your validation definitions.
Commits
-------
cb12f22 [FrameworkBundle] Avoid warming up the validator cache for non-existent classes
This PR was submitted for the master branch but it was merged into the 2.7 branch instead (closes#20505).
Discussion
----------
[DOMCrawler] Bug fixed
| Q | A
| ------------- | ---
| Branch? | master
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| License | MIT
| Doc PR | reference to the documentation PR, if any
Commits
-------
6c3150d [DOMCrawler] Bug fixed
This PR was merged into the 2.8 branch.
Discussion
----------
Fix annotation type for $context
| Q | A
| ------------- | ---
| Branch? | 2.8
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | -
| License | MIT
| Doc PR | -
Previous type ExecutionContextInterface was referring to a non declared namespace. Replacing it by ExecutionContextInterface2Dot5 fixes autocomplete.
Commits
-------
55e134c Fix annotation type for $context
This PR was merged into the 2.7 branch.
Discussion
----------
[Process] Do feat test before enabling TTY mode
| Q | A
| ------------- | ---
| Branch? | 2.7
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #20565
| License | MIT
| Doc PR | -
Commits
-------
69bfbbf [Process] Do feat test before enabling TTY mode
This PR was merged into the 3.1 branch.
Discussion
----------
[FrameworkBundle] Mark cache.default_*_provider services private
| Q | A
| ------------- | ---
| Branch? | 3.1
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #20563
| License | MIT
| Doc PR | -
I know making a service private has a potential for breaking BC. Yet, these services should not be used directly in controllers/userland code, and I really doubt anyone did. Let's make it private now and fix linked issue (even if it's a false positive from SymfonyServiceDefinitionValidator, it shows we have this service that really isn't meant to be public).
Commits
-------
09adfda [FrameworkBundle] Mark cache.default_*_provider services private
* 3.1:
[YAML] Fix processing timestamp with timezone
[ci] Testing with UTC hides bugs
[DI] Fix error when trying to resolve a DefinitionDecorator
[DoctrineBridge] Fix deprecation message/documentation of implementing UserProviderInterface using the entity provider
Fix time-sensitive tests that use data providers
[Validator] improve and added more Indonesian translation.
This PR was merged into the 3.1 branch.
Discussion
----------
[YAML] Fix processing timestamp strings with timezone
| Q | A
| ------------- | ---
| Branch? | 3.1
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #20399
| License | MIT
| Doc PR | -
Parse date strings containing timezone data correctly
Default date strings not containing timezone data to UTC
Commits
-------
cdb11a7 [YAML] Fix processing timestamp with timezone
* 2.8:
[ci] Testing with UTC hides bugs
[DI] Fix error when trying to resolve a DefinitionDecorator
[DoctrineBridge] Fix deprecation message/documentation of implementing UserProviderInterface using the entity provider
[Validator] improve and added more Indonesian translation.
* 2.7:
[ci] Testing with UTC hides bugs
[DI] Fix error when trying to resolve a DefinitionDecorator
[Validator] improve and added more Indonesian translation.
