Resolve historic tags
AllanJard opened this issue · comments
I've only just realised that the packages I have weren't being marked with release versions because I had a version attribute in my composer.json files. I had thought they were ignored, but apparently not - and I do see the warning message in the UI, I just hadn't seen it before now. Apologies!
The upshot is that my packages don't have release versions, and I'm wondering if there is a way to have packagist go back over the versions and build the release packages for them? Or if not that, then just the current release version rather than using the HEAD as it currently is?
Packagist does not build any release packages.
The only way to make older versions appear would be to re-tag them with correct metadata.
Forgive me, I'm not entirely sure what you mean. I have tag "1.13.8" in github, but packagist is showing only dev-master. How can I get it to show the existing releases (similar to this package)?
Basically, packagist only creates a new version when you create a new tag. It doesn't look at already existing, historical tags. Effectively, you have to create a new tag now that the composer.json has been fixed and it should pick it up.
your 1.13.8 tag is not a tag with correct metadata, as it has version: 1.12.1 in its composer.json.
Darn yes, I hadn't considered that even although I've fixed it at the head, it of course is still wrong on the tag. Doh. Sorry.
I'll make a new release so packagist can pick it up, but that might be a few days away.
Thank you for the quick feedback on this.