cli
cli copied to clipboard
semantic-release
:cl::round_pushpin: Setup automated semver compliant package publishing
The **@semantic-release/npm** package already contains an updated method to get the registry. This should also be used in the CLI npm module.
Changing this will be a breaking change, as existing saved NPM password would no longer be found, if we add a prefix. Alternative would be to not use a prefix...
Tho I am able to push & pull from public git repo, when I run `semantic-release-cli setup`, I'm asked the following question `Is the GitHub repository private?` When I say...
The info object has ghepurl property but it never gets populated. If I override it with our github host details I am able to get authorization tokens - `info.ghepurl =...
Hello there, I'm having some issues while I try to use the package, I can't login into my Github account. The last step I see in my terminal is "What...
When using a public GitHub repo, a token with the following scopes is created: ``` read:org, repo, repo:status, repo_deployment, user:email, write:repo_hook ``` Are all these necessary? In ye olde times...
As Gitlab is now fully supported by **semantic-release**, it should also be supported by the CLI. Tasks (that I can think of): - [ ] Add question for which git...
The **@semantic-release/npm** package determines the npm registry automatically (in `getRegistry`). There's no user intervention possible, and no environment variable to set to influence that either. That made me wonder what...
> This issue is to gather requirements for the refactoring of the CLI codebase ## Functional Adding more and more features to the CLI means that the flow becomes less...
Not sure what I'm doping that causes this, tbh... ``` ? What is your npm registry? https://registry.npmjs.org/ ? What is your npm username? simenb ? What is your npm password?...
Metadata
Owner
Metadata
:cl::round_pushpin: Setup automated semver compliant package publishing