docs: replace as such with therefore (#14069)

This commit is contained in:
HonkingGoose 2022-02-07 15:59:07 +01:00 committed by GitHub
parent faefb20917
commit b23dab14b3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions

View file

@ -2066,7 +2066,7 @@ Renovate's `"auto"` strategy works like this for npm:
5. Otherwise, replace the range. e.g. `"^2.0.0"` would be replaced by `"^3.0.0"`
By default, Renovate assumes that if you are using ranges then it's because you want them to be wide/open.
As such, Renovate won't deliberately "narrow" any range by increasing the semver value inside.
Therefore, Renovate won't deliberately "narrow" any range by increasing the semver value inside.
For example, if your `package.json` specifies a value for `left-pad` of `^1.0.0` and the latest version on npmjs is `1.2.0`, then Renovate won't change anything because `1.2.0` satisfies the range.
If instead you'd prefer to be updated to `^1.2.0` in cases like this, then configure `rangeStrategy` to `bump` in your Renovate config.

View file

@ -30,7 +30,7 @@ Be careful, and consider creating a new "config help" post at the [discussions t
## Commit Message
Renovate will use one commit per branch, this makes it easy for you to merge.
As such, the `commitMessage` reflects the contents of the branch and is usually the same as the PR title.
Therefore, the `commitMessage` reflects the contents of the branch and is usually the same as the PR title.
`commitMessage` has a default value of `{{commitMessagePrefix}} {{commitMessageAction}} {{commitMessageTopic}} {{commitMessageExtra}} {{commitMessageSuffix}}`, with the intention that you only edit some of those subcomponents.