Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

How about changing interpretation of version string

Open
#447 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
ci-cd

Research direction

Start by tracing how the ruby-version input is interpreted in GitHub Actions workflow files, using the reported 3.0 environment-value example as the motivating case. Define and verify the intended meanings for 3, 3.0, and 3.x, including the compatibility impact on existing workflows.

Written by the indexing model from the issue text.

Description

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.

Dominant language
JavaScript
Stars
990
Forks
369
Avg merge
18m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruby/setup-ruby

All issues in ruby/setup-ruby

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.