Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

v232 is not published in packagist.org #627

Open
boboldehampsink opened this issue Apr 4, 2023 · 6 comments
Open

v232 is not published in packagist.org #627

boboldehampsink opened this issue Apr 4, 2023 · 6 comments
Assignees
@dzuelke
Labels
bug

Comments

@boboldehampsink
Copy link

So composer update is not picking it up
@boboldehampsink
Copy link
Author

@dzuelke tagging you in case you missed it ;-)

@dzuelke dzuelke self-assigned this Apr 11, 2023
@dzuelke dzuelke added the bug label Apr 11, 2023
@dzuelke
Copy link
Contributor

dzuelke commented Apr 11, 2023

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.

@boboldehampsink
Copy link
Author

Ahh ok - you can't manually force an update on packagist.org for the time being?

@dzuelke
Copy link
Contributor

dzuelke commented Apr 11, 2023 •
edited

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.

@boboldehampsink
Copy link
Author

@dzuelke any update on this?

@boboldehampsink
Copy link
Author

Hi @dzuelke, any news?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dzuelke dzuelke

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dzuelke @boboldehampsink