-
Notifications
You must be signed in to change notification settings - Fork 48
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.
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
Is this project still maintained? #66
Comments
I replaced this action with name: Login to ACR
uses: docker/login-action@v3
with:
registry: <registry-name>.azurecr.io
username: ${{ secrets.AZURE_CLIENT_ID }}
password: ${{ secrets.AZURE_CLIENT_SECRET }} docker/login-action@v3 uses Node 20 as default runtime. |
Thank you @soderlind, that worked great for me |
My first time using Azure and following the instructions as seen in here. Lost quite a handful of hours figuring out why pushing to ACR on my GitHub Actions kept on failing with |
I came here looking if this has improved since I evaluated and rejected this action. Nothing has improved. It still has all the problems and now even more without node20.
For us it is better to just run |
it's not maintained anymore. Original team does not had bandwidth to maintain it. I just asked the access to upgrade to node20. that's it. don't expect any improvment/new feature which is not pushed by the community |
Last real update is from 2022, a nice PR updating to node 20 is open and needed, but ignored. As well as other open issues.
Is there still somebody here maintaining the action?
The text was updated successfully, but these errors were encountered: