Closed joshmedeski closed 3 months ago
That's weird because the PR I approved should not require any rebuild. I found more issues 1- the workflow doing unit testing says OK while it fails internally 2- I can't push a new branch to SSO specific configuration. it says that I have to reauth Visual Studio which I'm not using
I did a fork, but instead of just doing the rebuild, I upgraded the npm packagez. it should fix the known vulnerabilities and maybe fix some open issues. The problem is that it could bring to new bugs too. Since I can't create a branch here, could you please test this version: https://github.com/lgmorand/docker-login
lgmorand/docker-login@master
if some people (@joshmedeski @valimail-scott) can confirm it works for them before I do a PR. Thanks
shoot. it does not work. I even tried to rebuild the TS but it does not change anything
looks like node_modules have be missing. I'm looking when they have been removed
Looks fine on my side with added node_modules. What I don't understand is that I don't see them in this repo before the merge from yesterday.
anyway. please confirm that the fork works with you and I'll continue the merge and recreate the v2 release. thanks
I got this error when trying to test your fork. I'm not sure if master
is supported:
Error: Unable to resolve action
lgmorand/test-docker-login@master
, unable to find versionmaster
Have the exact same issue when upgrading azure/docker-login
from v1 to v2.
you have to test "lgmorand/docker-login@master" (see yaml file), not lgmorand/test-docker-login@master (which is a test repo to call the "forked" action. Normally it should work but since there are so many configurations possible, I'd love to have some people to test it first
with github actions, you can reference a tag, a branch or a commit.
Have the exact same issue when upgrading
azure/docker-login
from v1 to v2.
sure but did you test the forked one I put in the comments ? it would help a lot. thanks :)
Thanks for clarifying, the fork is working for me!
I recreated the tag v2 and the release. Closing the issue for now. don't hesitate for reopen an issue (or do a PR) if someone finds an issue
When I upgraded to v2, I got the following error:
Perhaps something wasn't built successfully on the recent release.