Lock internal dependencies to patch version

[benbrown]

Fixes #652

Description

Update all the package files to change dependency on other Botbuilder libraries from any minor release (^4.0.0) to the specific minor release (~4.1.x)

This means a user installing version 4.1.7 will get all 4.1 updates, but will not automatically migrate to 4.2 which could break things.

[coveralls]

Pull Request Test Coverage Report for Build 2242

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.06%) to 82.098%

---

Files with Coverage Reduction	New Missed Lines	%
libraries/botframework-config/src/botConfigurationBase.ts	2	85.59%

Totals
Change from base Build 2240:	-0.06%
Covered Lines:	2633
Relevant Lines:	3088

---

💛 - Coveralls

[stevengum]

Hey @benbrown, we leave these versions at 4.0.0 because we automatically bump the version numbers via this script which is run in the .travis.yml file via npm update-versions. I think we just need to change the internal dependencies from using "^" to "~".

@cleemullins /@JuanAr am I correct in my statements?

[benbrown]

@stevengum yes, we do update them as part of the build.

After consulting with @cleemullins I updated the versions on Github because I thought it better to have working internal consistency -- IE, how can we be pointing to ~4.1.6 if on Github the package file says the current version is 4.0.0?

IMHO we should keep the public record clean and consistent.

[stevengum]

I'm all for keeping the public record clean and consistent as long as we stay consistent going forward 😄

!

[benbrown]

@stevengum I have made an informal suggestion that we put together a shipping checklist that we run through every time we publish a new version that would include maintenance tasks like this! I will make roll up my sleeves and just do it soon.