Skip to content

Enabling the NuGetPackagesConfigDetector to run by default.#355

Merged
JamieMagee merged 1 commit into
mainfrom
users/avannikumar/EnableNuGetPackagesConfigDetector
Nov 8, 2022
Merged

Enabling the NuGetPackagesConfigDetector to run by default.#355
JamieMagee merged 1 commit into
mainfrom
users/avannikumar/EnableNuGetPackagesConfigDetector

Conversation

@amitla1
Copy link
Copy Markdown
Contributor

@amitla1 amitla1 commented Nov 8, 2022

The NuGetPackagesConfigDetector is no longer an expiremental detector. After going through validation, we are turning this detector on by default.

@amitla1 amitla1 requested a review from a team as a code owner November 8, 2022 17:42
@amitla1 amitla1 requested a review from grvillic November 8, 2022 17:42
@JamieMagee JamieMagee merged commit 4e847fb into main Nov 8, 2022
@JamieMagee JamieMagee deleted the users/avannikumar/EnableNuGetPackagesConfigDetector branch November 8, 2022 17:50
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Nov 8, 2022

👋 Hi! It looks like you modified some files in the Detectors folder.
You may need to bump the detector versions if any of the following scenarios apply:

  • The detector detects more or fewer components than before
  • The detector generates different parent/child graph relationships than before
  • The detector generates different devDependencies values than before

If none of the above scenarios apply, feel free to ignore this comment 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants