pestphp / pestphp/pest

[Bug]: composer update without an updated version

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

Nobody has claimed this yet.

bug
Dominant language
PHP
Stars
11.7k
Forks
538
Avg merge
4d 11h
Merged PRs (30d)
8

Description

What Happened

Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 4 updates, 0 removals

Upgrading raxon/desktop (dev-main ca56e51 => dev-main 64d4efd)
Upgrading raxon/framework (dev-main b93a0ba => dev-main a63106e)
Upgrading sebastian/code-unit (3.0.3 => 3.0.3)
Upgrading sebastian/code-unit-reverse-lookup (4.0.1 => 4.0.1)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 4 updates, 0 removals
Downloading sebastian/code-unit (3.0.3)
Downloading sebastian/code-unit-reverse-lookup (4.0.1)
Downloading raxon/framework (dev-main a63106e)
Downloading raxon/desktop (dev-main 64d4efd)
Upgrading sebastian/code-unit (3.0.3 => 3.0.3): Extracting archive
Upgrading sebastian/code-unit-reverse-lookup (4.0.1 => 4.0.1): Extracting archive
Upgrading raxon/framework (dev-main b93a0ba => dev-main a63106e): Extracting archive
Upgrading raxon/desktop (dev-main ca56e51 => dev-main 64d4efd): Extracting archive
What is happening with the code-unit repository, why no new patch or minor version increase but why is it upgrading ?
I am using those through Pest-php and also got earlier an abandend state of some repositories related to it ?

How to Reproduce

composer update

Sample Repository

No response

Pest Version

3.8.4

PHP Version

8.4.13

Operation System

Linux

Notes

No response

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.

Research direction

Reproduce the report with composer update using Pest 3.8.4 and PHP 8.4.13, then inspect the lock-file output for sebastian/code-unit. Done means determining whether the dependency changed or was only refreshed at the same version, and documenting the cause or a concrete fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
devtools, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
40/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.