From 60da8f71d69b5678b158b045b5435d7d445a71ae Mon Sep 17 00:00:00 2001 From: Dilum Aluthge Date: Sat, 7 Mar 2026 14:24:05 -0500 Subject: [PATCH] README: Fix another typo in the docs for `min-minor` --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b59be0a..b7d3728 100644 --- a/README.md +++ b/README.md @@ -140,7 +140,7 @@ You can either specify specific Julia versions or version ranges. If you specify - `'nightly'` will install the latest nightly build. - `'1.7-nightly'` will install the latest nightly build for the upcoming 1.7 release. This version will only be available during certain phases of the Julia release cycle. - `'min'` is equivalent to `min-minor`. -- `'min-minor'` will install the earliest supported major/minor version of Julia compatible with the project. Especially useful in monorepos. Note: `min-minor` chooses the lowest major/minor, but gives the latest patch. For example, for a Julia `[compat]` entry of `julia = "1.10"`, `min-minoe` would resolve to e.g. `1.10.11` (NOT `1.10.0`). +- `'min-minor'` will install the earliest supported major/minor version of Julia compatible with the project. Especially useful in monorepos. Note: `min-minor` chooses the lowest major/minor, but gives the latest patch. For example, for a Julia `[compat]` entry of `julia = "1.10"`, `min-minor` would resolve to e.g. `1.10.11` (NOT `1.10.0`). - `'min-patch'` will install the earliest supported major/minor/patch version of Julia compatible with the project. For example, for a Julia `[compat]` entry of `julia = "1.10"`, `min-patch` would resolve to e.g. `1.10.0`. Internally the action uses node's semver package to resolve version ranges. Its [documentation](https://github.com/npm/node-semver#advanced-range-syntax) contains more details on the version range syntax. You can test what version will be selected for a given input in this JavaScript [REPL](https://repl.it/@SaschaMann/setup-julia-version-logic).