This happens with the new patch-folder naming for libraries and updating to a newer patch-version of an H5P content type.
The previous behavior was to create a new folder for major- and minor-version updates. For patch level updates the new library files replaced the old files, folder name did not change.
Now that the patch-version is a part of the folder name, a new folder is created for patch-version updates, and the old folder is deleted. For major- and minor-version updates there's no change, the previous version is kept.
The URL to the icon is cached by the Resources API, it has a 24h expire.
For major- and minor-version updates there is no change, the icon will be read from the previous version until the cache expires.
For patch-version updates the cached icon URL will be invalid since the files are written to a new folder and the old deleted. When the cache expires the icon will be read from the new folder.
This happens with the new patch-folder naming for libraries and updating to a newer patch-version of an H5P content type.
The previous behavior was to create a new folder for major- and minor-version updates. For patch level updates the new library files replaced the old files, folder name did not change.
Now that the patch-version is a part of the folder name, a new folder is created for patch-version updates, and the old folder is deleted. For major- and minor-version updates there's no change, the previous version is kept.
The URL to the icon is cached by the Resources API, it has a 24h expire. For major- and minor-version updates there is no change, the icon will be read from the previous version until the cache expires. For patch-version updates the cached icon URL will be invalid since the files are written to a new folder and the old deleted. When the cache expires the icon will be read from the new folder.