[4.x]: Unable to Upgrade Plugins in Craft CMS 4.8.0

[Selvavinoth1]

What happened?

Description

In Craft CMS version 4.8.0, there is an issue preventing the successful upgrade of installed plugins using the command php craft update (plugin). Interestingly, when upgrading the plugin on an older version of Craft CMS, such as 4.7.1, the plugin upgrade functions as expected.

Steps to reproduce

1. Open the Terminal and log in.
2. Navigate to the respective project directory.
3. Upgrade Craft CMS to version 4.8.0.
4. Execute the plugin upgrade command using php craft update .
5. Verify the plugin version in the admin dashboard.

Expected behavior

Executing the plugin update command should reflect the changes in the admin dashboard or project files.

Actual behavior

Although the update command indicates that the update and migration processes are completed in the terminal, the new version fails to impact the admin dashboard when checked. The expected changes are not reflected in the admin dashboard.

Craft CMS version

4.8.0

PHP version

8.2

Operating system and version

Linux

Database type and version

MySql

Image driver and version

No response

Installed plugins and versions

No response

[brandonkelly]

Just tested locally and verified plugins are in fact getting updated properly.

Is your composer.json file getting updated as a result, at least? If not, double-check that you’re updating the right Craft install.

[webzones-git]

Yes, in composer.json file the latest version is getting updated but not on the affecting to the plugin files.

[Selvavinoth1]

Additionally, I'd like to provide more details on this issue. While I can install new plugins without any problems, I am encountering difficulties when attempting to update the existing ones.

[brandonkelly]

Is this happening locally or on a server?

[Selvavinoth1]

The issue that is reported is happening on the server.

[brandonkelly]

Any chance we could get access to it, to test it ourselves? If so, please send SSH credentials over to support@craftcms.com.

[Selvavinoth1]

No, we can't share the SSH details of the server, any chance you could test the same from your end?

[brandonkelly]

I did test it, and had no problem updating a plugin. And we haven’t received any other reports of this, so there’s probably something specific to your environment that is causing this.

Can you give us some details about your environment? Anything that could be out of the ordinary?