On Thu, Apr 2, 2020 at 3:35 PM Eric Citaire <[email protected]> wrote:

>
> I really don't like breaking things and I was wondering if there were a
> way to avoid this and still be able to move forward. Dependant plugins are
> able to declare a minimum version of a dependency, but not a maximum
> version. Is there any way for me to declare a breaking change in the plugin
> manifest?
>

https://wiki.jenkins.io/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtJuzFCYPVq-4upmixeVy%2B1623Y4SSt0Tb3xqZj1QYh%2Bhw%40mail.gmail.com.

Reply via email to