Point cqm-models at master instead of a non-existent branch.

[rbclark]

Builds are currently failing since the the results_object_mongoize no longer exists on cqm-models ever since the changes were merged in projecttacoma/cqm-models#42

Submitter:

• This pull request describes why these changes were made.
• Internal ticket for this PR: (N/A)
• Internal ticket links to this PR (N/A)
• Code diff has been done and been reviewed
• Tests are included and test edge cases (N/A)
• Tests have been run locally and pass (N/A)

Reviewer 1:

Name: @okeefm

• Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
• The tests appropriately test the new code, including edge cases
• You have tried to break the code

Reviewer 2:

Name:

• Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
• The tests appropriately test the new code, including edge cases
• You have tried to break the code

[okeefm]

A needed fix. master seems to be the right branch, as that's what results_object_mongoize was merged into in projecttacoma/cqm-models#42. Looks good to me.

[lmd59]

@rbclark Looks like there are some vulnerability problems with the thor gem at this point? Maybe should figure how to update before pulling in?

Name: thor
Version: 0.20.0
Advisory: CVE-2016-10545
Criticality: Unknown
URL: rails/thor#514
Title: Command injection in Thor Gem
Solution: remove or disable this gem until a patch is available!
Vulnerabilities found!

[rbclark]

I just re-ran the bundle-audit job, based on the linked URL the vulnerability isn't actually valid and the decision to create a CVE for it has been reversed.