Release Notes NuGet 6.2 #2744

martinrrm · 2022-05-05T16:56:36Z

I haven't cleaned the file yet, just created it

NuGet/NuGet.Client@release-6.1.x...release-6.2.x

opbld32 · 2022-05-05T16:57:26Z

Docs Build status updates of commit f1c9be1:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs/release-notes/NuGet-6.2.md	⚠️Warning	View	Details

docs/release-notes/NuGet-6.2.md

Line 4, Column 9: [Warning: author-not-found - See documentation] Invalid value for author: '<GithubAlias>' is not a valid GitHub ID.
Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', '<MicrosoftAlias>' is not a valid Microsoft alias.
Line 16, Column 7: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'NuGetVersion' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 16, Column 71: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'VSYear' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 16, Column 88: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'VSVersion' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 16, Column 151: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SDKVersion' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 18, Column 44: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'VSYear' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

JonDouglas · 2022-05-05T17:15:26Z

@jebriede Can you help with small blurbs for #11486, #10752, #10751, #10748, #10749

@zivkan Any thoughts on a blurb for nanoFramework?

@jeffkl Are you okay with re-using our blog portions?

@nkolev92 Any idea for blurb on #11671?

I'll create a few commits with all the feature blurbs.

nkolev92 · 2022-05-05T23:56:00Z

I think Add support for a dedicated environment variable providing the NuGetScratch path is pretty good.

I'd probably remove the feature prefixes from issues titles.

We should also consider not including the sub features of larger feature in the main part.
Right now it's not immediately obvious what the most valuable part in What's New is.

Our tooling/labeling probably needs special considerations :)

nkolev92

Thanks for getting this going!

A common thing when we use automation is that sometimes the description are not very user friendly. :)

Added some suggestions.

docs/release-notes/NuGet-6.2.md

nkolev92 · 2022-05-06T00:01:53Z

docs/release-notes/NuGet-6.2.md

+
+* Introduce a warning for null/empty version range (new or reuse NU1604) - [#9767](https://github.com/NuGet/Home/issues/9767)
+
+* NuGet restore in VS should report progress to allow the project-system to better control design time build scheduling.  - [#9782](https://github.com/NuGet/Home/issues/9782)


This should be a feature: NuGet/Home#9782.

We should include in the features with the title Add IVsNuGetProjectUpdateEvents in Visual Studio, reporting of restore changes for PackageReference based projects. https://docs.microsoft.com/en-us/nuget/visual-studio-extensibility/nuget-api-in-visual-studio#ivsnugetprojectupdateevents-interface

Should the link to the documentation be added in the release notes?

We can do it.
Usually we don't have everything document at release, so adding it would be nice I tihnk.

docs/release-notes/NuGet-6.2.md

…eature from bugs section

opbld32 · 2022-05-09T04:55:48Z

Docs Build status updates of commit 1e5bce8:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs/release-notes/NuGet-6.2.md	⚠️Warning	View	Details

docs/release-notes/NuGet-6.2.md

Line 4, Column 9: [Warning: author-not-found - See documentation] Invalid value for author: '<GithubAlias>' is not a valid GitHub ID.
Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', '<MicrosoftAlias>' is not a valid Microsoft alias.
Line 16, Column 7: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'NuGetVersion' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 16, Column 71: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'VSYear' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 16, Column 88: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'VSVersion' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 16, Column 151: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SDKVersion' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 18, Column 44: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'VSYear' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

nkolev92

LGTM.

docs/release-notes/NuGet-6.2.md

nkolev92 · 2022-05-09T20:42:48Z

docs/release-notes/NuGet-6.2.md

+
+<sup>1</sup> Installed with Visual Studio <VSYear> with.NET Core workload
+
+## Summary: What's New in 6.2


This looks great to me.

nkolev92 · 2022-05-09T20:44:28Z

Actually maybe we should do a known issue change for NuGet/Home#11564.

I think I'm supposed to write something for that.

I'll try to write up it later today.

opbld36 · 2022-05-09T23:48:25Z

Docs Build status updates of commit 70bf599:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs/release-notes/NuGet-6.2.md	⚠️Warning	View	Details

docs/release-notes/NuGet-6.2.md

Line 30, Column 187: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/nuget/visual-studio-extensibility/nuget-api-in-visual-studio#ivsnugetprojectupdateevents-interface' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 30, Column 187: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/nuget/visual-studio-extensibility/nuget-api-in-visual-studio#ivsnugetprojectupdateevents-interface' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

docs/release-notes/NuGet-6.2.md

opbld36 · 2022-05-09T23:52:39Z

Docs Build status updates of commit f17bc41:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/release-notes/NuGet-6.2.md	💡Suggestion	View	Details

docs/release-notes/NuGet-6.2.md

Line 30, Column 187: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/nuget/visual-studio-extensibility/nuget-api-in-visual-studio#ivsnugetprojectupdateevents-interface' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

nkolev92 · 2022-05-10T03:36:52Z

docs/release-notes/NuGet-6.2.md

+
+* NuGet.exe list from local packages folder does not work with the AllVersion flag - [#4537](https://github.com/NuGet/Home/issues/4537)
+
+* Project A referencing package B via AssetTargetFallback, doesn't use that same AssetTargetFallback to pull B's dependency package C - [#5957](https://github.com/NuGet/Home/issues/5957)


I wrote up a guide for the ATF change, maybe we can link it? NuGet/Samples#53

In particular I want to:

Get the samples PR reviewed and merged.

Add a comment linking that here.

cc @JonDouglas

Do you think we should add this to the notable changes list?

Do we want to add a Known issues section or something like that?

Maybe we have a better that mentions that this issue has consequences.

Open to ideas.

The link should be https://github.com/NuGet/Samples/tree/main/AssetTargetFallbackTransitiveDependencies.

@dominoFire suggests that we can add More info and link to the example, in particular https://github.com/NuGet/Samples/tree/main/AssetTargetFallbackTransitiveDependencies.

Pushed this.

Should be complete now.

known issues best for anything that is known with the release and will addressed soon or has significant limitations when using today.

This one is basically, you might have some weirdness, but there's no proposed changes right now.

See More Information, what we have right now, might work better for that.

Feel free to tweak if you think it's necessary

opbld31 · 2022-05-10T18:02:15Z

Docs Build status updates of commit 8a6c550:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/release-notes/NuGet-6.2.md	💡Suggestion	View	Details

docs/release-notes/NuGet-6.2.md

Line 30, Column 187: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/nuget/visual-studio-extensibility/nuget-api-in-visual-studio#ivsnugetprojectupdateevents-interface' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld36 · 2022-05-10T21:41:27Z

Docs Build status updates of commit 23647e4:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/release-notes/NuGet-6.2.md	💡Suggestion	View	Details

docs/release-notes/NuGet-6.2.md

Line 30, Column 187: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/nuget/visual-studio-extensibility/nuget-api-in-visual-studio#ivsnugetprojectupdateevents-interface' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld35 · 2022-05-10T21:44:59Z

Docs Build status updates of commit 8338693:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs/release-notes/NuGet-6.2.md	⚠️Warning	View	Details

docs/release-notes/NuGet-6.2.md

Line 30, Column 187: [Warning: file-not-found - See documentation] Invalid file link: '../visual-studio-extensibility/nuget-api-in-visual-studio'.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld36 · 2022-05-10T21:49:51Z

Docs Build status updates of commit cd87c03:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/release-notes/NuGet-6.2.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

dominoFire · 2022-05-12T03:00:14Z

Is there something left to do? Can I merge this PR?

opbld32 · 2022-05-12T20:36:40Z

Docs Build status updates of commit fd31628:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/release-notes/NuGet-6.2.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld31 · 2022-05-13T20:35:57Z

Docs Build status updates of commit 8612961:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/release-notes/NuGet-6.2.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

opbld35 · 2022-05-13T22:05:41Z

Docs Build status updates of commit b0f597e:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/release-notes/NuGet-6.2.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Try searching the docs.microsoft.com contributor guides
Post your question in the Docs support channel

JonDouglas

Do feel free to merge with what we have today. I will likely go back and update feature call outs and such later.

nkolev92 · 2022-05-16T19:20:37Z

Can we get them merged to live?

release notes

f1c9be1

nkolev92 reviewed May 6, 2022

View reviewed changes

Moved bugs from feature section, deleted still opens section, moved f…

1e5bce8

…eature from bugs section

JonDouglas mentioned this pull request May 9, 2022

Update Central-Package-Management.md #2745

Closed

nkolev92 approved these changes May 9, 2022

View reviewed changes

fixes

70bf599

martinrrm commented May 9, 2022

View reviewed changes

docs/release-notes/NuGet-6.2.md Outdated Show resolved Hide resolved

martinrrm commented May 9, 2022

View reviewed changes

docs/release-notes/NuGet-6.2.md Outdated Show resolved Hide resolved

localization fix

f17bc41

nkolev92 reviewed May 10, 2022

View reviewed changes

nkolev92 mentioned this pull request May 10, 2022

Add AssetTargetFallback transitive dependencies example for the docs. NuGet/Samples#53

Merged

Add a more information link

8a6c550

Fixed dotnet SDK version

23647e4

use a relative link

8338693

use a relative link

cd87c03

dominoFire mentioned this pull request May 10, 2022

Moves unshipped NuGet 6.2 APIs to PublicAPI.Shipped.txt files NuGet/NuGet.Client#4621

Merged

8 tasks

Added footer and link. Added missing bugfix

fd31628

Fernando Aguilar added 2 commits May 12, 2022 19:45

WiP: Community contributions

6514808

WiP: Community PRs

8612961

completed community contributions table

b0f597e

dominoFire requested review from JonDouglas and dominoFire May 13, 2022 22:19

JonDouglas approved these changes May 14, 2022

View reviewed changes

dominoFire merged commit d19c291 into main May 14, 2022

dominoFire deleted the NuGet-6.2 branch May 14, 2022 23:12

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Release Notes NuGet 6.2 #2744

Release Notes NuGet 6.2 #2744

martinrrm commented May 5, 2022

opbld32 commented May 5, 2022

JonDouglas commented May 5, 2022 •

edited

Loading

nkolev92 commented May 5, 2022

nkolev92 left a comment •

edited

Loading

nkolev92 May 6, 2022

martinrrm May 9, 2022

nkolev92 May 9, 2022

opbld32 commented May 9, 2022

nkolev92 left a comment

nkolev92 May 9, 2022

nkolev92 commented May 9, 2022

opbld36 commented May 9, 2022

opbld36 commented May 9, 2022

nkolev92 May 10, 2022

nkolev92 May 10, 2022

nkolev92 May 10, 2022

nkolev92 May 10, 2022

JonDouglas May 10, 2022

nkolev92 May 10, 2022

opbld31 commented May 10, 2022

opbld36 commented May 10, 2022

opbld35 commented May 10, 2022

opbld36 commented May 10, 2022

dominoFire commented May 12, 2022

opbld32 commented May 12, 2022

opbld31 commented May 13, 2022

opbld35 commented May 13, 2022

JonDouglas left a comment

nkolev92 commented May 16, 2022


		* Introduce a warning for null/empty version range (new or reuse NU1604) - [#9767](https://github.com/NuGet/Home/issues/9767)

		* NuGet restore in VS should report progress to allow the project-system to better control design time build scheduling. - [#9782](https://github.com/NuGet/Home/issues/9782)


		<sup>1</sup> Installed with Visual Studio <VSYear> with.NET Core workload

		## Summary: What's New in 6.2


		* NuGet.exe list from local packages folder does not work with the AllVersion flag - [#4537](https://github.com/NuGet/Home/issues/4537)

		* Project A referencing package B via AssetTargetFallback, doesn't use that same AssetTargetFallback to pull B's dependency package C - [#5957](https://github.com/NuGet/Home/issues/5957)

Release Notes NuGet 6.2 #2744

Release Notes NuGet 6.2 #2744

Conversation

martinrrm commented May 5, 2022

opbld32 commented May 5, 2022

⚠️ Validation status: warnings

JonDouglas commented May 5, 2022 • edited Loading

nkolev92 commented May 5, 2022

nkolev92 left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

opbld32 commented May 9, 2022

⚠️ Validation status: warnings

nkolev92 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nkolev92 commented May 9, 2022

opbld36 commented May 9, 2022

⚠️ Validation status: warnings

opbld36 commented May 9, 2022

✅ Validation status: passed

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

opbld31 commented May 10, 2022

✅ Validation status: passed

opbld36 commented May 10, 2022

✅ Validation status: passed

opbld35 commented May 10, 2022

⚠️ Validation status: warnings

opbld36 commented May 10, 2022

✅ Validation status: passed

dominoFire commented May 12, 2022

opbld32 commented May 12, 2022

✅ Validation status: passed

opbld31 commented May 13, 2022

✅ Validation status: passed

opbld35 commented May 13, 2022

✅ Validation status: passed

JonDouglas left a comment

Choose a reason for hiding this comment

nkolev92 commented May 16, 2022

JonDouglas commented May 5, 2022 •

edited

Loading

nkolev92 left a comment •

edited

Loading