Skip to content

Plugin version constraints#

Plugin version constraints allow you to limit which plugin versions can be used to generate SDKs for a repository. When plugins have bugs, breaking changes, or security vulnerabilities, constraints allow you to prevent consumers from depending on problematic SDKs.

How plugin constraints work#

When you add constraints to a repository:

  1. SDK generation only uses plugin versions that satisfy all constraints.
  2. Package managers that support latest resolve to the newest version that meets your constraints.

Setting up plugin constraints#

  1. Navigate to your repository in the BSR and click the Settings icon at top-right.
  2. Find Manage available plugin versions.
  3. Click Add plugin constraint.
  4. Search for and select the desired plugin.

  5. Choose an operator and version based on your needs:

    Operator When to use Example scenario
    >= Enforce minimum version >= 2.1.0 when older versions lack required features
    != Block specific version != 1.4.2 to exclude a version with security issues
    < Prevent newer versions < 3.0.0 when v3+ introduces incompatible changes
    > Exclude older versions > 1.0.0 to block outdated 1.x versions
    == Lock to exact version == 2.5.1 for strict version control

  6. Add additional combinations of operators and versions to suit your use case. Multiple conditions are combined using logical AND.

  7. Click Save constraint when you're done.