Pin agogosml library version in cli output

[sayar]

All Submissions:

• [x] Have you followed the guidelines in our Contributing document?

• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

• [x] Does your PR follow our Code of Conduct?

• [x] Have you added an explanation of what your changes do and why you'd like us to include them?

• [x] Does each method or function "do one thing well"? Reviewers may recommend methods be split up for maintainability and testability.

• [x] Is this code designed to be testable?

• [x] Is the code documented well?

• [x] Does your submission pass existing tests (or update existing tests with documentation regarding the change)?

• [x] Have you added tests to cover your changes?

• [x] Have you linted your code prior to submission?

• [x] Have you updated the documentation and README?

• [x] Is PII treated correctly? In particular, make sure the code is not logging objects or strings that might contain PII (e.g. request headers).

• [x] Have secrets been stripped before committing?

[cicorias]

this seems to only ensure that agogosml is at a specific version - which is good and generally this would dictate that semantic versioning is followed. although using 0.xx as a versioning strategy probably should be avoided and just start with 1.x - and start pushing major version updates when things WILL break - which is now often. exact version in requirements (==) always imho work best.

[sayar]

this seems to only ensure that agogosml is at a specific version - which is good and generally this would dictate that semantic versioning is followed. although using 0.xx as a versioning strategy probably should be avoided and just start with 1.x - and start pushing major version updates when things WILL break - which is now often. exact version in requirements (==) always imho work best.

I agree so I'm pinning to exact major.minor versions. Patches are still picked up this way.