Description
What version?
0.49.2
Which command?
proto outdated --update
What happened?
When I define a SemVer range in my .prototools file, calling the command will override the version with the latest it found based on the SemVer range. Now calling it again will, since SemVer is no longer existing, update it to the latest release it finds.
This causes several issues:
- Sometimes hardcoded versions (no SemVer range) are required if no update can be done due to upstream issues
- Repeating calls could jump between patch and minor releases, which can cause incompatibilities
I would suggest the following:
Install the exact version (or range) as described in the .prototools, do not override the definition, but create a .protolock which includes the "found" upstream versions that have been installed (and pinned) to this project.
On update, check for version (or range) in .prototools, check against .protolock if an update is necessary. Update the .protolock if newer versions are available based on the definition. Never override the definition.
Additionally, I would suggest separating outdated and update, then update could get a flag --latest (like pnpm) which ignores the definition.
Trace logs?
No response
Operating system?
MacOS
Architecture?
arm64