Upgrade to windows 0.39.0

[Frederick888]

Just got hit by the security alert. Since there hasn't been any news at
#18 for a while, here's another one to bump it directly to 0.37.0.

[MeerMusik]

@allenbenz

Hello. I hope it is only time that prevents you from working on this Project and ignoring Merge Requests?

As other Projects rely on this currently:

If you do not have time (currently / anymore) for whatever reason to work on this, it would be nice to update the ReadMe or create a pinned Issue and let People know.

This cloud help that someone(TM) maybe Fork it and become the new Maintainer and create a new official Crate, or you could try to find a Maintainer for this Repo officially.

Thank you in advance and have a nice Day!

[izzy]

Is this going to see any updates? I'm using a larger framework, which is using this lib, which in turn is using the outdated windows lib that throws security errors.

Given that this lib hasn't seen an update since January, the maintainer has had no activity on GH since March and has no contact info on their GH profile I think some clarification on the status of this project would be nice, so upstream maintainers can decide on how to deal with the downstream security issue in windows.

[MeerMusik]

Is this going to see any updates? I'm using a larger framework, which is using this lib, which in turn is using the outdated windows lib that throws security errors.

Given that this lib hasn't seen an update since January, the maintainer has had no activity on GH since March and has no contact info on their GH profile I think some clarification on the status of this project would be nice, so upstream maintainers can decide on how to deal with the downstream security issue in windows.

Well you said it yourself:
The Admin / Maintainer of this Repo does not react so far. Your only hope currently IMHO is, to create an Issue in the Repo of the Framework you are using, tell them what is going on and also at the same time, asks them to remove any Dependency to this crate or alternatively add that Functionality directly to the Framework - in one way or another.

This is what I would do, if I choose for example Tauri (the Framework I am testing) and Rust instead of Wails and Go (Golang).

As I have not yet decided which Framework I am going to use, I have not created a Report at the Tauri Repo myself so far.

Another Alternative: Someone(TM) else creates a Fork of this Repo and upload / publish it as a new Crate. But so far there seems no one (myself included) to either have the time, knowledge and or interest to do this.

[Frederick888]

Alternatively someone can backport microsoft/windows-rs@afe3252 to 0.24.0 and release it as 0.24.1, which is probably more efficient in terms of tackling this particular security issue.

[kmod-midori]

During my recent development on a side project, I came across this project, which has been quite useful. However, I needed some more advanced features in Windows's toast APIs (such as header and some callbacks), so I wrote this crate and just published it. It is still somehow incomplete, but certainly usable.

It also contains registration code ported from Microsoft's community toolkit, so you will no longer need the PowerShell workaround and can directly register your application.

If you are a direct user of this crate, feel free to try out my crate (documentation might take some more time to build and show up).

[Frederick888]

There's also news at hoodie/notify-rust#148

[BeiyanYunyi]

@chengyuhui My notify-win-rs is relying on your winrt-toast now, come on!