Originally created by @gowizzard on GitHub (Nov 30, 2022).
Hello everyone, I have a small understanding question and wanted to clarify this here briefly. If I have a higher version number, should it be major update or rather major >? The same would intressieren me also for smaller version numbers, whether one should write now minor downgrade or minor <.
Maybe someone here can answer this question. Thank you in advance.
Originally created by @gowizzard on GitHub (Nov 30, 2022).
Hello everyone, I have a small understanding question and wanted to clarify this here briefly. If I have a higher version number, should it be `major update` or rather `major >`? The same would intressieren me also for smaller version numbers, whether one should write now `minor downgrade` or `minor <`.
Maybe someone here can answer this question. Thank you in advance.
Thank you, but what if I compare two versions? Then I would probably say major, minor or patch update. I have not found anything specific in the documentation.
Generally it's just about comparing different version numbers, which I implemented in a small project. I just want to make sure that my output is correct. Here you can find the example from my repository.
@gowizzard commented on GitHub (Nov 30, 2022):
Thank you, but what if I compare two versions? Then I would probably say major, minor or patch update. I have not found anything specific in the documentation.
Generally it's just about comparing different version numbers, which I implemented in a small project. I just want to make sure that my output is correct. [Here](https://github.com/gowizzard/compver#compare-versions) you can find the example from my repository.
If you compare two versions, i'd just indeed say "major/minor/patch update", or "major/minor/patch downgrade" (altho downgrades don't really happen often).
I'd suggest looking into https://npmjs.com/semver for an npm-specific example of comparison and ranges.
@ljharb commented on GitHub (Nov 30, 2022):
If you compare two versions, i'd just indeed say "major/minor/patch update", or "major/minor/patch downgrade" (altho downgrades don't really happen often).
I'd suggest looking into https://npmjs.com/semver for an npm-specific example of comparison and ranges.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @gowizzard on GitHub (Nov 30, 2022).
Hello everyone, I have a small understanding question and wanted to clarify this here briefly. If I have a higher version number, should it be
major updateor rathermajor >? The same would intressieren me also for smaller version numbers, whether one should write nowminor downgradeorminor <.Maybe someone here can answer this question. Thank you in advance.
@ljharb commented on GitHub (Nov 30, 2022):
"major version", i'd say.
@gowizzard commented on GitHub (Nov 30, 2022):
Thank you, but what if I compare two versions? Then I would probably say major, minor or patch update. I have not found anything specific in the documentation.
Generally it's just about comparing different version numbers, which I implemented in a small project. I just want to make sure that my output is correct. Here you can find the example from my repository.
@ljharb commented on GitHub (Nov 30, 2022):
If you compare two versions, i'd just indeed say "major/minor/patch update", or "major/minor/patch downgrade" (altho downgrades don't really happen often).
I'd suggest looking into https://npmjs.com/semver for an npm-specific example of comparison and ranges.
@gowizzard commented on GitHub (Nov 30, 2022):
Okay, thank you! Then I have already installed the correct formulations.