v232 is not published in packagist.org
boboldehampsink opened this issue · comments
So composer update is not picking it up
@dzuelke tagging you in case you missed it ;-)
Thank you @boboldehampsink, I had indeed missed this.
It might take a while to untangle this. No ETA. The cause is an IP allow list that's now in place on the heroku
GitHub org.
Ahh ok - you can't manually force an update on packagist.org for the time being?
Nope, not possible, it needs API access to the releases even for that.
It shouldn't be a biggie though, since nothing has changed in the "usable" part of the buildpack for a while, so you can keep using the latest published version.