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

--stability=rc is treated as dev

Open Beginner friendly
#67 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
php
Domain
cli

Research direction

Start in src/Environment/Stability.php, where Stability::toInt() maps the value passed by --stability to a weight and returns 0 for unknown input. Make the lookup case-insensitive so rc and RC both resolve to the RC weight. Done when --stability=rc rejects 3.5.0-beta.1 and still accepts RC and stable releases. The acceptance test VersionSelectionTest::prefersReleaseCandidateOverOlderBeta is mentioned in #66, so check whether it exists in your branch before relying on it.

Written by the indexing model from the issue text.

Description

bug

Description

--stability=rc (lower case, the spelling Composer and RoadRunner tags use) is not recognised: Stability only knows RC. The command prints Possibly invalid stability (--stability=rc) and then Stability::toInt() maps the unknown value to weight 0, so the minimum stability silently becomes dev and alpha/beta releases are accepted too.

Expected: rc and RC are the same stability, as in Composer; --stability=rc admits only RC and stable releases.

Steps to reproduce

  1. With releases v3.5.0-rc.1, v3.5.0-beta.1 and v3.4.0, run rr get --stability=rc --filter=3.5.0-beta.1.
  2. The beta is installed instead of failing the stability check; --stability=RC rejects it.

Additional context

Found by the acceptance tests in #66 (VersionSelectionTest::prefersReleaseCandidateOverOlderBeta, together with #58: lower-case -rc tags also sort below -beta ones). The release lookup may be replaced by DLoad in #49.

Dominant language
PHP
Stars
30
Forks
15
Avg merge
9h 37m
Merged PRs (30d)
16

Getting set up

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.

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.