Usually the best technique is to accept that users who update plugins to newer releases are also users who update their Jenkins versions.
- Over 80% of installations of Bitbucket plugin 1.11.0 are running Jenkins 2.204.1 or newer
- Over 60% of all installations of Bitbucket plugin are running Jenkins 2.204.1 or newer
I chose 2.204.1 as the new basis for the git plugin and git client plugin on the assumption that if they are not updating Jenkins, they probably won't update the plugin even if I release it. If they are updating Jenkins, then they will probably also update to a new version of the plugin.
Choosing a new Jenkins minimum version is not a breaking change. Users running older Jenkins versions won't be offered the new release.
You may also find it helpful as a new plugin maintainer to enable the plugin BOM to help manage dependency versions and to enable Dependabot and Release Drafter to remove some of the "rote work" of maintaining dependencies.
Dependency management is a good beginning, continuing in
plugin BOM ,
Mark Waite