Maintain versioned releases

[ryansburgoyne]

It would be really helpful if instead of a single release that always has the latest version, each release was maintained and tagged with a unique version.
I am automatically pulling from the release in a CI/CD pipeline and because I was using an older version on my development machine I wasn't aware that a breaking change had been made in the latest version.

[gtreshchev]

You could select bForceByPayload if you want to keep the behavior of the plugin as it was in the past.

As for versioning, for historical reasons, I don't create separate versions of plugins but strive to keep all the functionality working and stable in the latest plugin version. This is done because the plugins aren't that big and don't provide such comprehensive functionality to require separate versioning. Anyway, feel free to add more information about the problem, and I'll try to help you with the issue.

[ryansburgoyne]

Thanks for the response! Essentially I automatically download the plugin to my build server when I deploy my application that depends on it. Because there is no versioning mechanism, when the plugin's interface changed (by adding a new argument to the callback), my application failed to build until I updated the application code. It wasn't a big deal in this case, but it would be nice to be able to point to a stable version that won't change until I manually update.

If this isn't something you want to do, of course I could host my own versioned builds, but I wanted to make the suggestion as it would be helpful for my use case.