Package is missing on packagist.org
Closed this issue · 11 comments
Hi
Great work with the extension.
We'd like to use it in our projects but currently, it is not listed on packagist.org.
Can you submit it there?
Also, can we get this merged: #8 ?
I have merged magento 2.4 support but it is not fully compatible with magento 2.3 so it was tagged with a new minor version (see readme here https://github.com/creatuity/magento2-interceptors)
As for publishing on packagist, someone with permissions would be required.
@majql can you help with this? Simply submitting repo url here https://packagist.org/packages/submit should do it.
Sorry for late answer @fsw.
https://packagist.org/packages/creatuity/magento2-interceptors
@majql can i bother you again and ask to enable auto update:
https://packagist.org/about#how-to-update-packages
This way new versions will be published with tags.
Hi @majql Awesome! Can you also enable auto-update? https://packagist.org/about#how-to-update-packages
Omg, guys, I have just notice that you were pinging me since April and it looked like I ignored it. No, sorry, that's not the case. Issue fixed, I'll be more responsive on this since now.
Package has auto-updates enabled in Packagist now. Yay. However here's the output of manual sync:
"Some tags were ignored because of a version mismatch in composer.json"
@fsw could you please correct "1.3.2" tag location and move it to the most recent commit - 84fe729. I see that composer.json is corrected in that one and says "1.3.1" in the commit tagged "1.3.2".
@fsw please remove the "version" field from the composer.json altogether. It serves no purpose but to get in the way with Packagist tags.
@peterjaap AFAIK version might be useful when using package without Packagist, I will make sure from now on it is tagged correctly.
@majql fixed tag. package looks good on packagist thanks. closing this.