semantic-versioning

问题 How can i bump the package.json version to contain -alpha using npm versioning. Running npm version <new version> will bump the version of the package.js file, however i want to add -alpha postfix to the version, but i am unable to as it is not stated in the documentation, but its supported by semver itself. Actual Result: > npm version prerelease > v0.2.1-1 Expected Result: > v0.2.1-alpha 回答1: While -alpha and -beta are common prerelease tags, they are not defined by SemVer. -alpha.1, -alpha

问题 I am about to release a Python library I've been working on the past few weeks. I've read a lot about Python dependencies but something is not quite clear yet: Some people pretend you should never pin your dependencies versions as it would prevent the users of your library from upgrading those dependencies. Some other claim that you should always pin your dependencies versions as it is the only way of guaranteeing that your release works the way it did when you developped it and to prevent

问题 I am about to release a Python library I've been working on the past few weeks. I've read a lot about Python dependencies but something is not quite clear yet: Some people pretend you should never pin your dependencies versions as it would prevent the users of your library from upgrading those dependencies. Some other claim that you should always pin your dependencies versions as it is the only way of guaranteeing that your release works the way it did when you developped it and to prevent

问题 I am about to release a Python library I've been working on the past few weeks. I've read a lot about Python dependencies but something is not quite clear yet: Some people pretend you should never pin your dependencies versions as it would prevent the users of your library from upgrading those dependencies. Some other claim that you should always pin your dependencies versions as it is the only way of guaranteeing that your release works the way it did when you developped it and to prevent

问题 In Countinous Delivery book, it's recommended to keep everything - including CI scripts - in the version control. Actually, current CI systems like gitlab CI already follow this rule of thumb and search for CI scripts in the same codebase. On the other hand, we are versioning our codebase (and it's built artifacts) whenever it changes. And we follow semantic versioning for that; incrementing patch field for bugfixes, minor for non-breaking features, and so on... And we make sure the version

问题 There is a very handy npm version command. Besides arguments like major , minor and patch it accepts arguments like prerelease , prepatch , etc. It says in the docs that the commands work in accordance with the semver.inc function. These pre commands I have a question about. Say I'm currently at version v1.0.0 . If I run npm version prerelease it will bump version to v1.0.1-0 . Is it possible to provide an extra agrument for a prerelease identifier according to https://github.com/npm/node

问题 I am developing an npm package and realized that it is added with the exact version to the package.json when adding it with npm i -S packagename How can I tell it to use ^0.0.1 instead of 0.0.1 ? Can I define this as the default from within the package itself? 回答1: That happens because ^0.0.1 is considered to be equivalent to 0.0.1 . When the version of a package starts with 0 it's considered to be in development, and the semantic versioning rules are different. An increase in either of the

问题 I have a npm package in my package.json file "clean-webpack-plugin": "^0.1.18" Now when I hover over the package I can see that there is a newer version "clean-webpack-plugin": "^0.1.19" Now, as I understood, I could for example do npm update to update all packages obeying the semver rules or just the package npm update clean-webpack-plugin . So the caret ^ symbol should mean, that you could possibly update the packge to version 0.9.9 if available, right? npm update has no effect, that's why

问题 I'm trying to use a portable Python interpreter therefore I installed WinPython and plan to deploy my application to other machines someday. For my application I need to use a NLP module "spaCy". I tried to install spaCy on WinPython ( pip install -U spacy ), but it can not be installed. When it installs the module dependencies, a module "semver" seems can not be installed: Collecting semver (from sputnik<0.10.0,>=0.9.2->spacy) Using cached semver-2.7.6.tar.gz Complete output from command

问题 Seems like a pretty basic question, but I can't really figure out an "easy" way to do it. I'd like to sort a character vector containing semantic version numbers with base R functionality : vsns <- c("1", "10", "1.1", "1.10", "1.2", "1.1.1", "1.1.10", "1.1.2", "1.1.1.1", "1.1.1.10", "1.1.1.2") It should look like this after sorting: # [1] "1" "1.1" "1.1.1" "1.1.1.1" "1.1.1.2" "1.1.1.10" # [7] "1.1.2" "1.1.10" "1.2" "1.10" "10" This doesn't get me what I want, of cours, as R simply sorts the