You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Repository does not return new package version if a new version version was created after the first connection to the repository
To Reproduce
Steps to reproduce the behavior:
clear cache by deleting the content of the repository servers cache directory (optional step)
run composer show -a vendorname/packagename
create a new tag in gitlab
run composer show -a vendorname/packagename again
-> new version is not be shown
Expected behavior
the new version should be listed
Additional context
the repository should recognize the new version data in the cache/module directory which is successfully updated by the gitlab webhoks. This issue was caused by the new userbased caching, and may be solved by ching the last modification time of other files before using the user cache.
The text was updated successfully, but these errors were encountered:
Describe the bug
Repository does not return new package version if a new version version was created after the first connection to the repository
To Reproduce
Steps to reproduce the behavior:
-> new version is not be shown
Expected behavior
the new version should be listed
Additional context
the repository should recognize the new version data in the cache/module directory which is successfully updated by the gitlab webhoks. This issue was caused by the new userbased caching, and may be solved by ching the last modification time of other files before using the user cache.
The text was updated successfully, but these errors were encountered: