Fetch upstream #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I'm trying to test symfony 6, But I'm getting this error ``` stof/doctrine-extensions-bundle dev-master requires symfony/config ^4.4 || ^5.2 -> found symfony/config[v4.4.0-BETA1, ..., 4.4.x-dev, v5.2.0-BETA1, ..., 5.4.x-dev] but these were not loaded, likely because it conflicts with another require. ```
Supporting symfony 6
Add a CI job running on PHP 8.1
This avoids having to update it for each release.
the sentence is given by @weaverryan in PR #443
add a note about updating schema
Remove deprecations alerts from sf5.4
…ns (Chris8934) This PR was merged into the main branch. Discussion ---------- chore: add ci tests for php 8.2, bump github action versions Will fix deprecations for Node 12 on github action runs. Commits ------- 169eac9 chore: add ci tests for php 8.2, bump github action versions
This PR was merged into the 1.x-dev branch. Discussion ---------- Fix symfony 6.3 return type deprecations > Method "Symfony\Component\DependencyInjection\Extension\ExtensionInterface::load()" might add "void" as a native return type declaration in the future. Do the same in implementation "Stof\DoctrineExtensionsBundle\DependencyInjection\StofDoctrineExtensionsExtension" now to avoid errors or add an explicit `@return` annotation to suppress this message. > Method "Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface::process()" might add "void" as a native return type declaration in the future. Do the same in implementation "Stof\DoctrineExtensionsBundle\DependencyInjection\Compiler\ValidateExtensionConfigurationPass" now to avoid errors or add an explicit `@return` annotation to suppress this message. > User Deprecated: Method "Symfony\Component\HttpKernel\Bundle\Bundle::build()" might add "void" as a native return type declaration in the future. Do the same in child class "Stof\DoctrineExtensionsBundle\StofDoctrineExtensionsBundle" now to avoid errors or add an explicit `@return` annotation to suppress this message. Commits ------- 3b5a8a2 Fix symfony 6.3 return type deprecations
Symfony 6.3 deprecated the registration of Doctrine subscribers because they cannot be lazy-loaded properly. The CI will ensure that the list of events is in sync with the library.
Register listeners instead of subscribers
Drop support for PHP 7.& and Symfony 4
Add support for IpTraceable
Configure the metadata cache for the extensions
Allow the bundle to work without Annotation Reader enabled in Symfony
Fix event listeners for Symfony 7
Add PHPStan
Fix the tests when doctrine/annotations is not installed
Drop support for PHP 7.2 and 7.3
When the `clock` service is defined (which is done by FrameworkBundle when `symfony/clock` is installed), it will be injected in the listeners supporting a clock integration.
Add the configuration for the Clock integration
Migrate to typed properties
Those classes are meant to be used only as implementation of the bundle semantic configuration, not directly.
This bundle does not rely on the extra (deprecated) features provided in the HttpKernel base class.
Remove usage of the deprecation HttpKernel base extension class
This avoids triggering the fallback path of instantiating an (uncached) annotation reader in the extensions in case annotations are disabled in FrameworkBundle but the `doctrine/annotations` package is still installed.
Inject an AttributeReader when annotations are disabled
feat: handling sf deprecation suppression
ci: Add tests for PHP 8.4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.