-
Notifications
You must be signed in to change notification settings - Fork 27
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
Error when upgrading to v2.0.0 (Cannot assign Pyrech\ComposerChangelogs\Config\Config to property) #81
Comments
Hi @adrenth I released v2 a few days ago so you might be the first to experience this issue. Sorry for that. I guess this is due to some class that were renamed but Composer keep some cache for each plugin. I will try to reproduce the issue and fix it asap. Thanks |
Can confirm clear-cache fixed this for me too PHP Fatal error: Uncaught TypeError: Typed property Pyrech\ComposerChangelogs\ChangelogsPlugin_composer_tmp0::$config must be an instance of Pyrech\ComposerChangelogs\Model\Config or null, Pyrech\ComposerChangelogs\Config\Config used in phar:///usr/bin/composer/src/Composer/Plugin/PluginManager.php(221) : eval()'d code:111
Stack trace:
#0 phar:///usr/bin/composer/src/Composer/Plugin/PluginManager.php(221) : eval()'d code(41): Pyrech\ComposerChangelogs\ChangelogsPlugin_composer_tmp0->setupConfig()
#1 phar:///usr/bin/composer/src/Composer/Plugin/PluginManager.php(345): Pyrech\ComposerChangelogs\ChangelogsPlugin_composer_tmp0->activate()
#2 phar:///usr/bin/composer/src/Composer/Plugin/PluginManager.php(233): Composer\Plugin\PluginManager->addPlugin()
#3 phar:///usr/bin/composer/src/Composer/Installer/PluginInstaller.php(103): Composer\Plugin\PluginManager->registerPackage()
#4 [internal function]: Composer\Installer\PluginInstaller->Composer\Installer\{closure}()
#5 phar:///usr/bin/composer/vendor/react/promise/src/React/Promise in phar:///usr/bin/composer/src/Composer/Plugin/PluginManager.php(221) : eval()'d code on line 111
Fatal error: Uncaught TypeError: Typed property Pyrech\ComposerChangelogs\ChangelogsPlugin_composer_tmp0::$config must be an instance of Pyrech\ComposerChangelogs\Model\Config or null, Pyrech\ComposerChangelogs\Config\Config used in phar:///usr/bin/composer/src/Composer/Plugin/PluginManager.php(221) : eval()'d code:111
Stack trace:
#0 phar:///usr/bin/composer/src/Composer/Plugin/PluginManager.php(221) : eval()'d code(41): Pyrech\ComposerChangelogs\ChangelogsPlugin_composer_tmp0->setupConfig()
#1 phar:///usr/bin/composer/src/Composer/Plugin/PluginManager.php(345): Pyrech\ComposerChangelogs\ChangelogsPlugin_composer_tmp0->activate()
#2 phar:///usr/bin/composer/src/Composer/Plugin/PluginManager.php(233): Composer\Plugin\PluginManager->addPlugin()
#3 phar:///usr/bin/composer/src/Composer/Installer/PluginInstaller.php(103): Composer\Plugin\PluginManager->registerPackage()
#4 [internal function]: Composer\Installer\PluginInstaller->Composer\Installer\{closure}()
#5 phar:///usr/bin/composer/vendor/react/promise/src/React/Promise in phar:///usr/bin/composer/src/Composer/Plugin/PluginManager.php(221) : eval()'d code on line 111
➜` |
@pyrech Maybe adding a note about it in the CHANGELOG would be enough. It's a simple fix once you know what to do. |
Sorry I did not find some time to dig this issue yet. @NicolasCARPi You're right, thanks for the suggestion, I just added a note in the CHANGELOG.md and the GitHub release |
When having v1.8.2 installed and upgrading to v2.0.0 you might get this error:
After clearing composer cache it should work fine.
However... can this behavior be prevented? Anyone else experienced this issue?
The text was updated successfully, but these errors were encountered: