Uploaded image for project: 'Libmongocrypt'
  1. Libmongocrypt
  2. MONGOCRYPT-183

Multiple different builds of libmongocrypt claim to be the same version

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 1.0.0-rc0
    • Affects Version/s: None
    • Component/s: None

      mongocrypt_version() returns a version like "1.0.0-beta4". This version is updated when a new release is tagged (like in https://github.com/mongodb/libmongocrypt/commit/91413d5c41c75201caa88a58744c240b21cd90a7).

      The problem here is that all the commits/builds in between two releases all share the same version number so there is no way to distinguish a user with the actual "1.0.0-beta4" build and one that's a few commits ahead.

      For reference the mongodb binaries avoid this problem by including the git SHA in the version as well as the number of commits ahead of the previous tag:

      $ mongodb-macos-x86_64-4.1.10-298-ga406d41/bin/mongo --version
      MongoDB shell version v4.1.10-298-ga406d41
      git version: a406d4152133336a2966ebae0612adc58244e7fd
      ...
      

            Assignee:
            kevin.albertson@mongodb.com Kevin Albertson
            Reporter:
            shane.harvey@mongodb.com Shane Harvey
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: