Update Microsoft.Graphics.Win2D package reference to version 1.3.0, downgrade TFM back to 19041

[Arlodotexe]

This PR updates our Win2d dependency to 1.3.0. Notably, this version has a minimum TFM of net6.0-windows10.0.19041, wheras the previous 1.1.1 version we were using has a minimum TFM of net6.0-windows10.0.22621.

Since this dependency was the only reason we originally bumped our Windows App SDK TFM to 22621 (see CommunityToolkit/Tooling-Windows-Submodule#161, microsoft/Win2D#943), we can follow-up with a submodule PR to reduce our TFM back down to 19041.

[ghost1372]

Tnx @Arlodotexe
is there any date for next release?

[Arlodotexe]

Tnx @Arlodotexe is there any date for next release?

Are you asking about the changing in this PR specifically, or for the toolkit in general?

[ghost1372]

Tnx @Arlodotexe is there any date for next release?

Are you asking about the changing in this PR specifically, or for the toolkit in general?

Toolkit.
My library is based on toolkit. (*.WinUI.Media nuget package)

[Arlodotexe]

Tnx @Arlodotexe is there any date for next release?

Are you asking about the changing in this PR specifically, or for the toolkit in general?

Toolkit. My library is based on toolkit. (*.WinUI.Media nuget package)

@ghost1372 A random PR isn't the best place to be asking, I recommend opening a new Discussion on GitHub or asking over on Discord in the future. We aim to release again before the end of the year, but our timeline can shift based on circumstances.

cc @michael-hawker, a suggestion for later-- Any time we ship, it would be good to pre-emptively open a Discussion thread for "the next release" for the community and ourselves. In the early stages, it can be used to gauge lingering needs or expectations of the community, and as we work towards that next release, we keep it updated with our general plans. That way, we can also link to it when asked. Worth consideration.

[ghost1372]

Tnx @Arlodotexe is there any date for next release?

Are you asking about the changing in this PR specifically, or for the toolkit in general?

Toolkit. My library is based on toolkit. (*.WinUI.Media nuget package)

@ghost1372 A random PR isn't the best place to be asking, I recommend opening a new Discussion on GitHub or asking over on Discord in the future. We aim to release again before the end of the year, but our timeline can shift based on circumstances.

cc @michael-hawker, a suggestion for later-- Any time we ship, it would be good to pre-emptively open a Discussion thread for "the next release" for the community and ourselves. In the early stages, it can be used to gauge lingering needs or expectations of the community, and as we work towards that next release, we keep it updated with our general plans. Worth consideration.

Thank you.
I think I misunderstood what you meant or I conveyed my meaning badly.
i am waiting for this change (19041 tfm) for CommunityToolkit.WinUI.Media package.
Therefore, I just wanted to know if this change will be published soon or not?(rc/preview release or even stable)

[Arlodotexe]

@ghost1372 I see, thank you for clarifying. We have NuGet feeds for PRs and for the main branch, see here: https://github.com/CommunityToolkit/Windows/wiki/Preview-Packages#available-preview-feeds

It's harder to give an exact date for when this would make it to stable-- we'd like to release a patch next week if we can.

[Arlodotexe]

Now needs CommunityToolkit/Tooling-Windows-Submodule#222