Shouldn’t this be Superseded:
5055981, Microsoft Edge Build 94.0.992.31 Available
5055983, Microsoft Edge x64 Build 94.0.992.31 Available
5056091, Microsoft Edge Stable Build 97.0.1072.55 Available
5056093, Microsoft Edge Stable Build 97.0.1072.55 Available (x64)
Same goes for:
5056102, Microsoft Edge Extended Stable Build 96.0.1054.57 Available
5056104, Microsoft Edge Extended Stable Build 96.0.1054.57 Available (x64)
These two we superseded will get published soon(5055981, Microsoft Edge Build 94.0.992.31 Available
5055983, Microsoft Edge x64 Build 94.0.992.31 Available).
These are security updates(5056091, Microsoft Edge Stable Build 97.0.1072.55 Available
5056093, Microsoft Edge Stable Build 97.0.1072.55 Available (x64)) hence we cant supersede these with non security update(97.0.1072.76 which is the latest update).
3.Even these are security update (5056102, Microsoft Edge Extended Stable Build 96.0.1054.57 Available
5056104, Microsoft Edge Extended Stable Build 96.0.1054.57 Available (x64)) which cant be superseded by non security update(96.0.1054.75).
I do understand what you are saying, but don’t completely agree.
“Microsoft Edge Stable Build 97.0.1072.55 Available” should by following the logic be replaced by “Microsoft Edge Stable Build 97.0.1072.69 Available”
<SNIP from https://docs.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel >
“Version 97.0.1072.69: January 20
Stable channel security updates are listed here.”
According to the Bigfix fixlet (ID 5056103 “Microsoft Edge Stable Build 97.0.1072.69 Available”) it’s Category is “Security Update”
This (ID 5056103) update is however superseded by ID 5056111, “Microsoft Edge Stable Build 97.0.1072.76 Available”, that’s not a Security update.
For the extended version I didn’t see the same “issue”.
Not that it really matter, since MS has scheduled Edge 98 to be released this days.
But with the info from you, I have to take this scenario into account for the automation.
Thank you for the insight into what makes a fixlet superseded.
In patch we usually follow this approach for supersedence,
We Supersede Security updates by next security update and non security update by next non security update or by next security update. But we will not supersede security updates by non security updates.