How about changing interpretation of version string

Many users who wants use 3.0.x write ruby-version: 3.0 by mistake.

3.0 interpreted as 3 on GitHub Actions.

For example, following workflow step prints 3 only.

        env:
          env_var: 3.0
        run: |
          set -x
          echo ${env_var}

So I propose changing the meaning of 3 (and 3.0 on workflow files) use 3.0.x, and 3.x (or something) use latest 3.x.x.

After this change, many users can write 3.0 intentionally, and some (probably less) users who want use latest 3.x.x can write 3.x or something instead.

首先追蹤 ruby-version input 在 GitHub Actions 工作流程檔案中的解讀方式，以回報的環境值 3.0 範例作為動機案例。定義並驗證 3、3.0 和 3.x 的預期含義，包括對現有工作流程相容性的影響。