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

Releases with non-version tags are named d-<tag> instead of dev-<tag>

Open Beginner friendly
  • Is something wrong?
#61 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/Repository/Release.php at simplifyReleaseName(), which cuts the last two characters of the first dash-separated part and so turns dev-nightly into d-nightly. Read GitHubRelease::getTagName() in src/Repository/GitHub/GitHubRelease.php for the dev- fallback that already works. Remove the #[Skip] on fromApiResponseNamesUnparsableReleaseAsDevBranch in tests/Unit/Repository/GitHub/GitHubReleaseTest.php, then run vendor/bin/testo --filter=fromApiResponseNamesUnparsableReleaseAsDevBranch; done when that test passes and numeric versions still lose only their trailing .0. Issue #49 may replace this lookup, so check it first.

Written by the indexing model from the issue text.

Description

bug

Description

A GitHub release whose tag and name are not valid versions is named d-<tag> instead of dev-<tag>. For a release with tag_name: nightly and name: Nightly, getName() returns d-nightly. The versions command shows this name, and satisfies() checks constraints against it.

GitHubRelease::getTagName() correctly falls back to dev-nightly. Release::simplifyReleaseName() then normalizes the name, splits it on - and always cuts the last two characters of the first part. That step is meant to strip the .0 that VersionParser::normalize() appends to numeric versions (2024.1.0.0 becomes 2024.1.0), but for dev-nightly it turns dev into d.

Steps to reproduce

  1. Remove #[Skip] from GitHubReleaseTest::fromApiResponseNamesUnparsableReleaseAsDevBranch.
  2. Run vendor/bin/testo --filter=fromApiResponseNamesUnparsableReleaseAsDevBranch.

Additional context

The release lookup may be replaced by DLoad in #49, in which case this code goes away.

Dominant language
PHP
Stars
30
Forks
15
Avg merge
45m
Merged PRs (30d)
11

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.

More from roadrunner-php/cli

All issues in roadrunner-php/cli

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.