GitHub Actions bot deleted the Surface driver catalog

[401cf609a3a217ec]

Describe the bug
GitHub Actions bot commit deleted all lines from the Surface driver catalog. The file is currently blank.

To Reproduce
Check the diff here: 4b3384a

Expected behavior
The file should not be empty.

Additional context
This has happened a few times previously, so adding some kind of validation prior to committing the changes could help catch this kind of bug.

[MichaelEscamilla]

Interesting, pinging @OSDeploy

[PaiSolutions]

Could this be why im not seeing any driver packs for my surface devices

[OSDeploy]

Should be restored in the next OSD update within the next few hours.

[401cf609a3a217ec]

The actions workflow cleared out the Surface catalog again:

14e5f6b#diff-b6e401424a8783bc2ebd206073a055cc093d12036e66d04f7ba51887c14d3d04

[OSDeploy]

The actions workflow cleared out the Surface catalog again:

14e5f6b#diff-b6e401424a8783bc2ebd206073a055cc093d12036e66d04f7ba51887c14d3d04

Does Surface actually work anyway? There's an issue where the MSI doesn't install in Specialize. I suppose I'm inclined to just remove them.

Have you tested the updated OSDCloud in the OSDCloud PS Module? If not, then I'm inclined to leave this as is.

[StevenVBeek]

The actions workflow cleared out the Surface catalog again:
14e5f6b#diff-b6e401424a8783bc2ebd206073a055cc093d12036e66d04f7ba51887c14d3d04

Does Surface actually work anyway? There's an issue where the MSI doesn't install in Specialize. I suppose I'm inclined to just remove them.

Have you tested the updated OSDCloud in the OSDCloud PS Module? If not, then I'm inclined to leave this as is.

That issue is fixed. Its working fine again in specialize.