This has been happening forever on the new and old launcher. There is no Valid digital signature. so the Publisher is blank. This only gives you a Security Warning till you tell it not to. not really a bug. This does not need to be fixed, Minecraft runs fine. Just thought I would post it, to let you know its there.
Linked issues
relates to 1
Attachments
Comments 13
There is no need to add launcher versions as labels, that is what the "Affects Version/s" field is for. Similarly, the OS is for the Environment, and the project type already says its for the launcher.
This issue has reappeared in launcher version 1.2.7 (issue didn't exist with version 1.2.5). Also, I'm going to toss this in here because I don't know where else to put it, but the launcher download webpage <http://minecraft.net/download> has the wrong date for the launcher's release...so if/when someone is doing what they should (double-checking the download of an unsigned executable that is presenting warnings), they then encounter an inconsistency between what the downloaded executable's created date is and the webpage's claim of what it should be.
Not fixed for Minecraft.exe (https://s3.amazonaws.com/Minecraft.Download/launcher/Minecraft.exe)
Alright, I assumed as it was linked to on https://minecraft.net/download that it is up to date as well and not only a workaround
Please do not mark unreleased versions as affected. You do not have access to this yet.