Closed peter-sition closed 3 years ago
Hi Peter, thanks for reporting. Can you make the repository available so that I can reproduce the bug? Right now I have tested the Bitbucket integration and everything works fine.
You can also check repository webhook history in Bibukcet: Repository -> Setting -> Webhooks -> Enable history:
And finally, one question: does manual synchronization help and the mentioned version appears in the repman?
[EDIT] Owke, the fault was at our side. There was an invalid composer.json 🤦
Using the Cloud version of Repman.io
Attached Bitbucket cloud to repman.io for use as private repository Added repository to repman.io with one tag in it: 1.0.0
We've 'released' a new version with the tag 1.0.1. In Bitbucket and in Git this tag is shown correctly. Also the version number in composer.json is correct.
Tried to following:
The result for both is that only the 1.0.0 tag is visible.