Test for updated doc. on latest/ranges/-rc

Author: paulo-ferraz-oliveira

README.md

@@ -55,11 +55,12 @@ end up being parsed as `23`, which is not equivalent.
 
 For pre-release versions, such as `v1.11.0-rc.0`, use the full version
 specifier (`v1.11.0-rc.0`) and set option `version-type` to `strict`. Pre-release versions are
-opt-in, so `1.11.x` will not match a pre-release.
+opt-in (unless you're using `latest`), so `1.11.x` will not match a pre-release.
 
 #### "Latest" versions
 
-Set a tool's version to `latest` to retrieve the latest version of a given tool.
+Set a tool's version to `latest` to retrieve the latest version of a given tool; this includes
+release candidates. If you want to exclude release candidates use a range such as `> 0`.
 The latest version is (locally) calculated by the action based on the (retrieved) versions
 it knows (**note**: it is not the same as [GitHub considers it](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository)
 and some repositories might propose).

test/setup-beam.test.js

@@ -885,6 +885,12 @@ describe('.getVersionFromSpec(_)', () => {
     got = setupBeam.getVersionFromSpec(spec, matrix.otp['ubuntu-24.04'])
     assert.deepStrictEqual(got, expected)
 
+    // range > 26 excludes -rc1, -rc2, and -rc3
+    spec = '> 26'
+    expected = 'OTP-26.0'
+    got = setupBeam.getVersionFromSpec(spec, matrix.otp['ubuntu-24.04'])
+    assert.deepStrictEqual(got, expected)
+
     spec = 'latest'
     expected = '27.0-rc3'
     got = setupBeam.getVersionFromSpec(spec, matrix.otp.windows)