Jurre
> Any news on this? Currently not on our roadmap. I'd suggest (for now at least) setting up an action (or any other CI job really) that runs after Dependabot...
Could we chat to the pipenv maintainers about improving the error messages? It would be a bummer to be stuck on an old version for a while
> Update - it does seem to work adequately by removing `ruby` as a platform on our side 🙌 . Again, thank you @deivid-rodriguez for the suggestion. > > @jurre...
I've opened https://github.com/dependabot/dependabot-core/pull/5465 which bumps us to the latest version of bundler, but I don't think a version with a fix for this issue has been released yet, so unfortunately...
> edit: I do wonder if you might consider downgrading bundler to the previously-working version until it's fixed? @kbarrette yeah, I'm open to it @deivid-rodriguez do you happen to know...
Thanks so much 🙇 I'll downgrade to `2.3.16` for now as we've also gotten some reports of this via our customer support, and once a new version is released with...
> Thanks, and sorry for too many regressions lately :( No need to apologize, so many different configurations out in the world that it's really hard to always spot all...
https://github.com/dependabot/dependabot-core/pull/5479 should resolve things for now
Can you show the config you're using and the error that you're getting?
Thanks! Typically ECR registry URLs look something like this: `123456789123.dkr.ecr.us-east-2.amazonaws.com`, it looks like our auth proxy is trying to authenticate to this registry as a regular docker registry (using OAuth)....