Question regarding automation with inconsitent release names and filenames

[pvillaverde]

Describe the bug

Hey there!

I had a Dockerfile for a custom rabbitmq image installing the plugin and I've noticed some inconsistency regarding the version and filenames in the release section and I'd like to know if there's been any discussion about it and there's a single naming going forward to adjust it accordingly

Reproduction steps

Release "3.10.2" didn't have the "v" prefix, nor did the filename to curl the download:
https://github.com/rabbitmq/rabbitmq-delayed-message-exchange/releases/download/3.10.2/rabbitmq_delayed_message_exchange-3.10.2.ez

Release "v4.0.7" does have the "v" prefix, and the filename does it too:
https://github.com/rabbitmq/rabbitmq-delayed-message-exchange/releases/download/v4.0.7/rabbitmq_delayed_message_exchange-v4.0.7.ez

However latest "v4.1.0" only has the "v" prefix in the release name, but not in the filename:
https://github.com/rabbitmq/rabbitmq-delayed-message-exchange/releases/download/v4.1.0/rabbitmq_delayed_message_exchange-4.1.0.ez

Expected behavior

I'd expect the release filenames to follow the same pattern in order to easily automate the Dockerfile to just pass the version argument and download the desired version of the plugin.

Additional context

No response

[gomoripeti]

There is so rarely a release of this plugin (maybe once every half year) that you can even manually lookup and enter the correct download link. Alternatively you could automatically try a few different download link combinations with or without v.

Don't misunderstand me, I am not sarcastic, what you would expect makes sense. But the build system changes more frequently than there is a new release of this plugin. And maintaining this whole plugin is not a priority for the RabbitMQ Core Team (which also makes sense as there will be a commercial alternative)

[pvillaverde]

There is so rarely a release of this plugin (maybe once every half year) that you can even manually lookup and enter the correct download link. Alternatively you could automatically try a few different download link combinations with or without v.

Don't misunderstand me, I am not sarcastic, what you would expect makes sense. But the build system changes more frequently than there is a new release of this plugin. And maintaining this whole plugin is not a priority for the RabbitMQ Core Team (which also makes sense as there will be a commercial alternative)

Hey there! Thanks for the anwer! That's the workarround I've used, passing other argument with the link. I understand it's not a priority, just pointing it out in case there was some standarization going on and for reference for other people!

[michaelklishin]

Now any scheme we pick for 4.2.0 will be "wrong" to someone, so the best I can offer is that we'll try to use the same naming as we did (unintentionally) for 4.1.0.