Add Chocolatey package updates in build pipeline or Actions

[Vacant0mens]

Is your feature request related to a problem? Please describe.

The listing for the rabbitmq chocolatey pacakge seems like it has gotten updates about once or twice per month. The latest package in there (for v3.11.17) was updated a day after the respective release on GitHub. The releases updated on Chocolatey.org seem to have followed closely to the releases on GitHub until the end of May this year.

Specifically, the rabbitmq/chocolatey-package repository lists 3.12.x as one if its branches, but there have been no 3.12.x releases to chocolatey yet. I also see that the 3.12 branch has been updated from 3.12.0 to 3.12.1 recently (committed by rabbitmq-ci), but neither of those have shown up on chocolatey yet. However, I don't see a 3.11 branch in the list for that repo.

Describe the solution you'd like

If it's not already there/available, is it possible to integrate the chocolatey-package repo into the build process so that the releases to Chocolatey are automatic alongside the GitHub releases?

Clearly there are (and/or were) already some elements of CI/automation to update the rabbitmq/chocolatey-package repository. Has support for Chocolatey been put on hold for some reason?

Describe alternatives you've considered

No response

Additional context

No response

[lukebakken]

Yes, we have an internal Concourse pipeline to publish to Chocolatey. Here is the current status:

When we have time we'll investigate why the pipelines aren't working correctly. Thanks for bringing this up.

[michaelklishin]

Those jobs started failing about a month ago. Could be an expired API key or something like that.

I don't think switching to Actions will meaningfully change anything in this regard.

[lukebakken]

We have fixed the CI build.