[Nightlies] Add windows nightly releases

[mowies]

Windows is currently excluded from nightly releases since there were some issues during initial implementation.

Look into those issues and add Windows to the nightly releases.

[douglascamata]

@mowies can you assign me to this issue, please?

Bringing in some info related to this before it becomes too difficult to find again:

• Example failed Windows nightly build: https://github.com/mowies/opentelemetry-collector-releases/actions/runs/16320666115/job/46097294661

• Error:

D:\a\opentelemetry-collector-releases\opentelemetry-collector-releases\distributions\otelcol\dist\windows_amd64\msi\otelcol_0.130.0-nightly.202507161321_windows_x64\otelcol_0.130.0-nightly.202507161321_windows_x64.wxs(2) : error CNDL0108 : The Product/@Version attribute's value, '0.130.0-nightly.202507161321', is not a valid version. Legal version values should look like 'x.x.x.x' where x is an integer from 0 to 65534.

Proposal on how to handle the situation: I think we can just not build the MSI installers for the nightlies. In reality, I believe that people running on the bleeding edge will most likely be using containers images rather than MSI installers.

[douglascamata]

While I investigate and try to work on a fix, I opened a discussion in GoReleaser requesting for a configuration setting under the nightly section to allow us to skip the MSI installer build: https://github.com/orgs/goreleaser/discussions/6010.

[douglascamata]

An alternative for us could be to release the nightly MSI simply with next version number (e.g. 0.199.3, without a -nightly.<date>) but with a "product name" that clearly indicates this is a nightly build for version X from day Y. I have no idea about the impact of changing this "product name" field in the UI of the installer, by the way. Not sure if it's clearly visible, for instance.

I actually prefer to do this so that we exercise the MSI build. I'm not sure if I will be able to make it to the next Collector call, but I will leave a note in the meeting agenda and ping some folks in Slack to get their opinion on this.

The conversation with the GoReleaser folks was successful though and there will be a way to disable MSI installer builds using templates in the next GoReleaser version: https://github.com/orgs/goreleaser/discussions/6010#discussioncomment-14181507. That's still pretty valid and helpful for many of the GoReleaser users besides us.

[pjanotti]

You should be able to do what you described above by keeping the current product naming

opentelemetry-collector-releases/distributions/otelcol-contrib/windows-installer.wxs

Line 3 in 87dcfba

Name="OpenTelemetry Collector ({{ .Version }}) - {{ .Binary }} distribution"

but changing

opentelemetry-collector-releases/distributions/otelcol-contrib/windows-installer.wxs

Line 6 in 87dcfba

Version="{{ .Version }}"

to be built using {{ .RawVersion }}.0 or leverage the templating to do something more sophisticated.

Changing the product name will be how it appears when you look at "installed products", however, it will have the same product id and upgrade code so for install/uninstall it will be treated as the same product.