publish(options: PublisherOptions): Promise<void>
win32artifacts to somewhere like GitHub on the first publish call, you will have to create the version on GitHub and the second call will just be appending files to the existing version. Your
publishimplementation will not be aware that another call is coming, however it must just be able to handle this case.
configfor the publisher will be available on