Versioning

BidJS follows semantic versioning.

This means versions look like the following: v1.2.3.

  • We change the first part of the version when we do a major, breaking change. This normally means that some effort is required to implement the upgrade
  • We change the second part of the version when we do a minor change, usually in a backwards-compatible manner. This could be a new feature.
  • We change the third part of the version when we do bugfixes. In reality, we don't expose this third number, so you'll always get bugfixes for your version as soon as we push them.

Versioning Options

In your setup, you will need to put in a version to your BidJS scripts.

You have a choice in how you subscribe to versions

Strict Versioning

If the current version is 3.1, you can simply put 3.1 as all of your versions.

This means that you'll get any bugfixes for 3.1.x as soon as we ship them.

However, it also means that you'll need to make a manual change once 3.2 comes out.

We recommend using strict versioning if you have many customisations, such as heavy CSS changes, or reliance on the BidJS Events as mentioned in our Advanced Configuration.

Loose Versioning

If the current version is 3.1, you can set your version as 3.

This means you'll get any bugfixes or new features within 3.x.x as soon as we ship them.

We recommend using loose versioning if you don't have a large number of customisations, as it means you're more likely to be up to date, getting all of our new functionality.