-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Exclusively use Azure (public) feeds #43303
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
Conversation
Didn't you say .npmrc doesn't work with yarn? |
I thought it didn't but everything was fine locally. |
Hey @dotnet/aspnet-build, looks like this PR is something you want to take a look at. |
e73309f
to
66f9ce7
Compare
@mmitche will we need a change like this in release/7.0❔ If yes, what about release/7.0-rc1❔ |
I recall the current emphasis is on our default branch but want to confirm. |
Can you explain what we need to do now with regards to npm dependencies, email is fine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the always_auth
params should be removed, but otherwise looks good
Thanks @mmitche, I'll remove the required auth in the next iteration here. Separately, this PR seems to add .npmrc files to the |
Never mind. Turns out all that happens is .npmrc files get copied to our node_modules/ folders when you do a local build. Final |
@BrennanConroy @TanayParikh @javiercn and anyone else who knows our local |
66f9ce7
to
e858f91
Compare
sent |
- fix what broke `yarn install` in these directories
- also correct a missing `--frozen-lockfile`
2020a7f
to
e073a6a
Compare
- was "Exclusively use Azure (public) feeds (#43303)" - Correct ref to selenium-config.json - fix what broke `yarn install` in these directories - Use `yarn` in aspnetcore-components-e2e pipeline - also correct a missing `--frozen-lockfile` Co-authored-by: MerlinBot
No description provided.