-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.10.0
-
Component/s: None
-
None
-
Environment:OS:
node.js / npm versions:
Additional info:
-
None
-
Developer Tools
Problem Statement/Rationale
The source code Github release of version `2.10.0` displays the wrong version number (`2.9.1`) when `mongosh --version` is run.
Steps to Reproduce
- Download the source code Github release for version 2.10.0 and extract it.
- Compile `mongosh` (`npm run bootstrap && npm run compile-cli`)
- Run with `–version` flag (`npm run -w @mongosh/cli-repl start – --version`)
Expected Results
`2.10.0` is displayed.
Actual Results
`2.9.1` is displayed.
Additional Notes
The culprit seems to be the tagged commit. The GitHub release is built from `0bed8dc0257fe32ff0d7d2431e48b993ea8ff3da`, but the version number in the `package.json` files is not bumped until the very next commit, `218840f94693358dde9573c146b9964f310eed8c`.
Interestingly enough, the prebuilt packages, circumvent this issue, so they've probably been compiled from a slightly more recent source. If this is the case, the source-binary mismatch would be another important issue in and of itself, since the user can fairly assume that the source code version and the binary version match and behave identically, but the released files don't satisfy this assumption.