Skip to content

chore: allow dev versions of ronasit/laravel-helpers - #78

Open
AZabolotnikov wants to merge 1 commit into
masterfrom
resolve-dev-relations
Open

chore: allow dev versions of ronasit/laravel-helpers#78
AZabolotnikov wants to merge 1 commit into
masterfrom
resolve-dev-relations

Conversation

@AZabolotnikov

Copy link
Copy Markdown
Contributor

No description provided.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4b3bf27349

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread composer.json
"phpunit/phpunit": ">=11.5.5",
"orchestra/testbench": ">=9.5.1",
"ronasit/laravel-helpers": ">=3.5.8",
"ronasit/laravel-helpers": "^3.5.8 || @dev",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep the dev allowance within the helpers version range

Composer treats || as a logical OR and a bare @dev as a stability flag without enforcing a version constraint, so this side is effectively unconstrained rather than ^3.5.8 with dev stability. In contexts such as composer update --prefer-lowest or when another dependency rules out helpers 3.x, this can now resolve ronasit/laravel-helpers to an older 1.x/2.x stable/dev branch even though the previous lower bound required at least 3.5.8, which can break the test helpers imported from that package; attach the stability flag to the intended constraint instead of adding it as a separate OR branch.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants