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

[Bug]: Laravel command de-sync

Open
#1,758 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
laravel, php
Domain
tooling

Research direction

The report gives no reproduction steps, no PHP version, and the community repository shows no version-detection code, so the first step is to gather detail: how the Laravel installer was installed, and the exact laravel --version output next to the version Herd displays. Reproduce by running laravel new and comparing that warning against Herd's installer panel after attempting an update. Done means CLI and Herd report the same installer version, or a maintainer confirms this must be fixed inside the app rather than in this repo.

Written by the indexing model from the issue text.

Description

macOS
Platform

macOS

Operating system version

macOS Tahoe 26.5.2 (25F84)

System architecture

ARM64 (M1, M2, etc)

Herd Version

1.30.1 (build 67)

PHP Version

No response

Bug description

Running laravel new from the command line tells me

   WARN  A new version of the Laravel installer is available. You have version 5.31.1 installed, the latest version is 5.32.0.

which isn't wrong, but going into Herd to update it and Herd thinks I'm running 5.32.0 so gives me no way to update it. I've confirmed that the only version of laravel on the system is inside of herd, and it is in fact not the latest version.

Image
Steps to reproduce

No response

Relevant log output

Dominant language
No language data
Stars
123
Forks
1
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 beyondcode/herd-community

All issues in beyondcode/herd-community

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.