-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Update YamlDotNet installation to use CFS #28981
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
base: main
Are you sure you want to change the base?
Conversation
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
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.
Pull request overview
This pull request modifies the YamlDotNet NuGet package installation in the sync-aliases.yml Azure Pipeline to use a local package source instead of the default NuGet feed. The change aims to improve build reproducibility and control over package versions by consuming YamlDotNet from a local repository location (./tools/LocalPackages) rather than from the public NuGet feed. The local package source contains YamlDotNet version 16.3.0.
Key changes:
- Registers a local NuGet package source pointing to
./tools/LocalPackages - Modifies package installation to use the local source instead of the default feed
- Removes the
RequiredVersionparameter andretryCountOnTaskFailuretask setting
|
|
88f1467 to
eb15642
Compare
eb15642 to
9fed6ac
Compare
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.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
Description
This pull request introduces a small update to the Azure Pipelines configuration by adding a NuGet authentication task. This ensures that any subsequent steps requiring access to private NuGet feeds will have the necessary credentials available.
NuGetAuthenticate@1task to the.azure-pipelines/sync-aliases.ymlpipeline, which configures authentication for NuGet operations.Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.