SemVer compatibility for 'yarn version <version>'

[vefydwy]

Since one of the last updates of the version plugin and with yarn v3.0.0 I get this error when trying to directly apply a version:

$ yarn version -i 2.0.0
➤ YN0001: UsageError: Invalid value for enumeration: "2.0.0" (expected one of "decline", "major", "minor", "patch", "prerelease")
    at Object.wge (C:\my\project\path\.yarn\releases\yarn-3.0.0.cjs:242:3029)
    at a2 (C:\my\project\path\.yarn\plugins\@yarnpkg\plugin-version.cjs:290:6352)
    at d2 (C:\my\project\path\.yarn\plugins\@yarnpkg\plugin-version.cjs:290:8667)
    at async C:\my\project\path\.yarn\plugins\@yarnpkg\plugin-version.cjs:292:5895
    at async Function.start (C:\my\project\path\.yarn\releases\yarn-3.0.0.cjs:275:2287)
    at async h2.execute (C:\my\project\path\.yarn\plugins\@yarnpkg\plugin-version.cjs:292:5710)
    at async h2.validateAndExecute (C:\my\project\path\.yarn\releases\yarn-3.0.0.cjs:197:620)
    at async ts.run (C:\my\project\path\.yarn\releases\yarn-3.0.0.cjs:211:1846)
    at async hd.execute (C:\my\project\path\.yarn\plugins\@yarnpkg\plugin-version.cjs:303:14147)
    at async hd.validateAndExecute (C:\my\project\path\.yarn\releases\yarn-3.0.0.cjs:197:620)
➤ YN0000: Failed with errors in 0s 12ms

Based on the help page it is still possible to directly specify a semver compliant version.

$ yarn version --help
Apply a new version to the current package

Usage

$ yarn version <strategy>

━━━ Options ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  -d,--deferred     Prepare the version to be bumped during the next release cycle
  -i,--immediate    Bump the version immediately

Details

This command will bump the version number for the given package, following the
specified strategy:

- If `major`, the first number from the semver range will be increased
  (`X.0.0`).

- If `minor`, the second number from the semver range will be increased
  (`0.X.0`).

- If `patch`, the third number from the semver range will be increased
  (`0.0.X`).

- If prefixed by `pre` (`premajor`, ...), a `-0` suffix will be set (`0.0.0-0`).

- If `prerelease`, the suffix will be increased (`0.0.0-X`); the third number
  from the semver range will also be increased if there was no suffix in the
  previous version.

- If `decline`, the nonce will be increased for `yarn version check` to pass
  without version bump.

- If a valid semver range, it will be used as new version.

- If unspecified, Yarn will ask you for guidance.

For more information about the `--deferred` flag, consult our documentation
(https://yarnpkg.com/features/release-workflow#deferred-versioning).

Examples

Immediately bump the version to the next major
  $ yarn version major

Prepare the version to be bumped to the next major
  $ yarn version major --deferred

With yarn version v2.4.2 and an earlier version of the "version" plugin the same command was successful.
(The sha256sum of that earlier plugin-version.cjs is "319f6c5f50390e867cfa4a073e41a7d1773a8db9c5fd770802338264dca1234d" - or do have plugins also versions? - At least I haven't found one.)

I can't find any info about this change in the documentation. Also the help page still says it's possible to directly apply a dedicated version. So either the help page is wrong or there is a bug in the plugin. What is the intended behaviour? Should I create an Issue?

Thanks and Regards,
Richard

[paul-soporan]

Opened #3322 to track this issue. I had to wait for #3310 to get merged so I could write a proper reproduction.