From ff27ebee2bc9f2d0fab9e6c17488be558d9601dc Mon Sep 17 00:00:00 2001 From: RahulGautamSingh Date: Mon, 27 Apr 2026 12:41:16 +0530 Subject: [PATCH] =?UTF-8?q?docs:=20use=20unicode=20arrow=20(=E2=86=92)=20i?= =?UTF-8?q?nstead=20of=20ASCII=20(->)=20(#42896)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * chore(docs): use unicode arrow (→) instead of ASCII (->) * more changes --- docs/usage/configuration-options.md | 16 ++++++++-------- docs/usage/dependency-pinning.md | 2 +- docs/usage/modules/versioning/index.md | 2 +- docs/usage/string-pattern-matching.md | 2 +- lib/data/readme.md | 10 +++++----- lib/modules/datasource/readme.md | 2 +- lib/modules/datasource/rubygems/readme.md | 2 +- lib/modules/manager/custom/regex/readme.md | 2 +- lib/modules/platform/scm-manager/readme.md | 2 +- 9 files changed, 20 insertions(+), 20 deletions(-) diff --git a/docs/usage/configuration-options.md b/docs/usage/configuration-options.md index d574aad2bc..2011d0290c 100644 --- a/docs/usage/configuration-options.md +++ b/docs/usage/configuration-options.md @@ -600,9 +600,9 @@ All messages are prefixed with `bumpVersions` or `bumpVersions()` to help It's possible to bump short versions: -- `1` -> `2` (major) -- `1.1` -> `2.0` (major) -- `1.2` -> `1.3` (minor) +- `1` → `2` (major) +- `1.1` → `2.0` (major) +- `1.2` → `1.3` (minor) ### `bumpVersions.bumpType` @@ -2347,7 +2347,7 @@ registry=https://gitlab.myorg.com/api/v4/packages/npm/ !!! note - Values containing a URL path but missing a scheme will be prepended with 'https://' (e.g. `domain.com/path` -> `https://domain.com/path`) + Values containing a URL path but missing a scheme will be prepended with 'https://' (e.g. `domain.com/path` → `https://domain.com/path`) ### `hostRules.maxRequestsPerSecond` @@ -3889,7 +3889,7 @@ For example to replace the npm package `jade` with version `2.0.0` of the packag Use the `replacementVersionTemplate` config option to control the replacement version. -For example, the following package rule can be used to replace version with major-only version (17.0.1 -> 17): +For example, the following package rule can be used to replace version with major-only version (17.0.1 → 17): ```json { @@ -4398,10 +4398,10 @@ You can configure `pruneStaleBranches=false` to disable deleting orphan branches Behavior: - `auto` = Renovate decides (this will be done on a manager-by-manager basis) -- `pin` = convert ranges to exact versions, e.g. `^1.0.0` -> `1.1.0` -- `bump` = e.g. bump the range even if the new version satisfies the existing range, e.g. `^1.0.0` -> `^1.1.0` +- `pin` = convert ranges to exact versions, e.g. `^1.0.0` → `1.1.0` +- `bump` = e.g. bump the range even if the new version satisfies the existing range, e.g. `^1.0.0` → `^1.1.0` - `replace` = Replace the range with a newer one if the new version falls outside it, and update nothing otherwise -- `widen` = Widen the range with newer one, e.g. `^1.0.0` -> `^1.0.0 || ^2.0.0` +- `widen` = Widen the range with newer one, e.g. `^1.0.0` → `^1.0.0 || ^2.0.0` - `update-lockfile` = Update the lock file when in-range updates are available, otherwise `replace` for updates out of range. Works for `bundler`, `cargo`, `composer`, `gleam`, `npm`, `yarn`, `pnpm`, `terraform`, `poetry` and `uv` so far - `in-range-only` = Update the lock file when in-range updates are available, ignore package file updates diff --git a/docs/usage/dependency-pinning.md b/docs/usage/dependency-pinning.md index 4fffcc30bb..0532706b47 100644 --- a/docs/usage/dependency-pinning.md +++ b/docs/usage/dependency-pinning.md @@ -80,7 +80,7 @@ So first of all, you can choose to read the changelogs and/or visually inspect t If you did not catch the fault before merging, you are still better off with a pinned version. If you discover something wrong in production, you can easily "roll back" commits in your development environment until you find which rollback fixes the problem. -Then you can simply revert that commit (reversing `foobar@1.1.0` -> `foobar@1.2.0`) and push that to `main`. +Then you can simply revert that commit (reversing `foobar@1.1.0` → `foobar@1.2.0`) and push that to `main`. When the next release of `foobar` comes out (e.g. `1.2.1`) you will be prompted with a new PR and hopefully inspect it carefully this time before merge! As you can see in the above, pinning dependencies makes your build more consistent and predictable as a developer. diff --git a/docs/usage/modules/versioning/index.md b/docs/usage/modules/versioning/index.md index 591eefbd19..1723642247 100644 --- a/docs/usage/modules/versioning/index.md +++ b/docs/usage/modules/versioning/index.md @@ -79,7 +79,7 @@ The configuration below overrides Renovate's default `docker` versioning for the In most ecosystems, especially SemVer, major upgrades are treated as breaking changes. But other updates may have breaking changes too, for example: -- In SemVer, any update from a 0.x version may be breaking (including `0.1.0` -> `0.1.1`, `0.1.0` -> `0.2.0` and `0.1.0` -> `1.0.0`) +- In SemVer, any update from a 0.x version may be breaking (including `0.1.0` → `0.1.1`, `0.1.0` → `0.2.0` and `0.1.0` → `1.0.0`) - Updates from pre-release versions like `1.0.0-pre.1` to other versions (including stable versions like `1.0.0`) can be breaking - Python makes breaking changes in minor updates, e.g. from `3.12` to `3.13` diff --git a/docs/usage/string-pattern-matching.md b/docs/usage/string-pattern-matching.md index aa424a7837..1fbb7a36e3 100644 --- a/docs/usage/string-pattern-matching.md +++ b/docs/usage/string-pattern-matching.md @@ -67,7 +67,7 @@ You can use the Code Generator in the sidebar and copy the regex in the generate !!! warning "Escape the backslashes from regex101" Before you copy/paste the regex from regex101 into your Renovate config, you must escape the backslashes (`\`) first. - For example: `\n\s` --> `\\n\\s`. + For example: `\n\s` → `\\n\\s`. ## Glob matching diff --git a/lib/data/readme.md b/lib/data/readme.md index 9032cc19fe..31a9b518a0 100644 --- a/lib/data/readme.md +++ b/lib/data/readme.md @@ -42,11 +42,11 @@ The `replacements.json` file has all the replacement presets. When a package gets renamed, you need to tell Renovate: -- the datasource of the package -> `matchDatasources` -- the old package name -> `matchPackageNames` -- the new package name -> `replacementName` -- the last version available for the old package name -> `matchCurrentVersion` -- the first version available for the new package name -> `replacementVersion` +- the datasource of the package → `matchDatasources` +- the old package name → `matchPackageNames` +- the new package name → `replacementName` +- the last version available for the old package name → `matchCurrentVersion` +- the first version available for the new package name → `replacementVersion` You can omit `replacementVersion` if the current version is the same as the new version. diff --git a/lib/modules/datasource/readme.md b/lib/modules/datasource/readme.md index 080adb03ad..c551ca481f 100644 --- a/lib/modules/datasource/readme.md +++ b/lib/modules/datasource/readme.md @@ -26,7 +26,7 @@ The config has: - `sourceUrl`: a HTTP URL pointing to the source code (for example on GitHub) - `homepage`: a HTTP URL for the package's homepage. Ideally should be empty if the homepage and `sourceUrl` are the same - `changelogUrl`: a URL pointing to the package's changelog (could be a Markdown file, for example). If not present then Renovate will search the `sourceUrl` for a changelog file -- `tags`: an object mapping tag -> version, for example `tags: { latest: '3.0.0' }`. This is only used by the `followTags` function +- `tags`: an object mapping tag → version, for example `tags: { latest: '3.0.0' }`. This is only used by the `followTags` function ## getDigest diff --git a/lib/modules/datasource/rubygems/readme.md b/lib/modules/datasource/rubygems/readme.md index a9078b5563..adc797af3d 100644 --- a/lib/modules/datasource/rubygems/readme.md +++ b/lib/modules/datasource/rubygems/readme.md @@ -11,7 +11,7 @@ This is implemented with two-level cache: Either full or delta sync is performed, depending on the cache state. - All the data of this layer is stored in-memory as the mapping `packageName -> version[]`. + All the data of this layer is stored in-memory as the mapping `packageName → version[]`. ```mermaid stateDiagram-v2 diff --git a/lib/modules/manager/custom/regex/readme.md b/lib/modules/manager/custom/regex/readme.md index 2e35d681b8..8c0ba8664e 100644 --- a/lib/modules/manager/custom/regex/readme.md +++ b/lib/modules/manager/custom/regex/readme.md @@ -93,7 +93,7 @@ something:4.7.2 something-else:4.7.2 If you're looking for an online regex testing tool that supports capture groups, try [regex101.com](). You must select the `ECMAScript (JavaScript)` flavor of regex. -Backslashes (`'\'`) of the resulting regex have to still be escaped e.g. `\n\s` --> `\\n\\s`. +Backslashes (`'\'`) of the resulting regex have to still be escaped e.g. `\n\s` → `\\n\\s`. You can use the Code Generator in the sidebar and copy the regex in the generated "Alternative syntax" comment into JSON. ##### Renovate's regex differs from the online tools diff --git a/lib/modules/platform/scm-manager/readme.md b/lib/modules/platform/scm-manager/readme.md index 6a991c9f52..32f54a2e12 100644 --- a/lib/modules/platform/scm-manager/readme.md +++ b/lib/modules/platform/scm-manager/readme.md @@ -27,7 +27,7 @@ Those permissions can be granted on a repository level within the permission set ## Install Review Plugin To let Renovate access the Pull Request API, you must install the Review Plugin with at least version 3.11.0. -Find the list of available plugins by going to Administration -> Plugins -> Available. +Find the list of available plugins by going to Administration → Plugins → Available. ## Supported versions of SCM-Manager