paketo-buildpacks
Failure: Push Buildpackage workflow
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This was caused by GHA being down. The CNB registry didn't respond before the action on our end hit the timeout. Even though the action timed out, the buildpack was successfully added to the registry: https://github.com/buildpacks/registry-index/issues/3255
Another failure occurred: https://github.com/paketo-buildpacks/nodejs/actions/runs/2883120567
Another failure occurred: https://github.com/paketo-buildpacks/nodejs/actions/runs/2883120567
The release was still published and the image pushed to all registry locations. The issue was a timeout from the CNB registry GHA: https://github.com/paketo-buildpacks/nodejs/actions/runs/2883120567/jobs/4581890378
Another failure occurred: https://github.com/paketo-buildpacks/nodejs/actions/runs/9764173539
@sophiewigmore I know we had some problems with the GitHub registry but I had thought it was only for paketo-community. Wanted to check if we expect the publishing to be ok in this repo?
I looks like the push to DockerHub was ok.
@mhdawson I think the job just needs a longer time out, the release made it into the registry eventually. If you click into the CNB Registry issue - https://github.com/buildpacks/registry-index/issues/8708, you can see that it did eventually make it in, our job just hit a timeout waiting
Btw I've just raised the timeout in https://github.com/buildpacks/github-actions/pull/289 which is now available in: https://github.com/buildpacks/github-actions/releases/tag/v5.7.3
Another failure occurred: https://github.com/paketo-buildpacks/nodejs/actions/runs/11736494362
The push workflow works fine. The error was due to removing the tag, and recreating a new release with that tag.
Another failure occurred: https://github.com/paketo-buildpacks/nodejs/actions/runs/15202717089
Another failure occurred: https://github.com/paketo-buildpacks/nodejs/actions/runs/18041750551