New version of spatie/laravel-model-info (2.0.4) broke the build

[depfu]

We've tested your project with an updated dependency and the build failed.

This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name	version specification	new version
spatie/laravel-model-info	^1.4	^2.0

Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.

If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)

We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of spatie/laravel-model-info for this test run.

What changed?

✳️ spatie/laravel-model-info (^1.4|^2.0 → 2.0.4) · Repo · Changelog

Release Notes

2.0.4

What's Changed

• Bump dependabot/fetch-metadata from 1.6.0 to 2.2.0 by @dependabot in #43
• Bump dependabot/fetch-metadata from 2.2.0 to 2.3.0 by @dependabot in #45
• Bump aglipanci/laravel-pint-action from 2.4 to 2.5 by @dependabot in #46
• Laravel 12.x Compatibility by @laravel-shift in #47

Full Changelog: 2.0.3...2.0.4

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 10 commits:

• Merge pull request #47 from laravel-shift/l12-compatibility
• Update GitHub Actions for Laravel 12
• Bump dependencies for Laravel 12
• Merge pull request #46 from spatie/dependabot/github_actions/aglipanci/laravel-pint-action-2.5
• Bump aglipanci/laravel-pint-action from 2.4 to 2.5
• Merge pull request #45 from spatie/dependabot/github_actions/dependabot/fetch-metadata-2.3.0
• Bump dependabot/fetch-metadata from 2.2.0 to 2.3.0
• Fix styling
• Merge pull request #43 from spatie/dependabot/github_actions/dependabot/fetch-metadata-2.2.0
• Update CHANGELOG

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[claude]

Pull Request Review - PR #153

Summary

This PR attempts to update spatie/laravel-model-info from ^1.4|^2.0 to a pinned version 2.0.4. The change was automatically created by Depfu to test compatibility with the new version, and the build has failed, indicating a breaking change or incompatibility.

---

Critical Issues

1. Pinned Version Anti-Pattern

Severity: High

The PR pins spatie/laravel-model-info to an exact version (2.0.4) instead of using semantic versioning.

Problems:

• Violates composer best practices for library packages
• Prevents users from receiving bug fixes and security patches in future 2.0.x releases
• Creates dependency conflicts for projects that use this package alongside other packages requiring different 2.0.x versions
• Not consistent with other dependencies in the project which use semantic versioning

Recommendation:
If version 2.0.4 is required, use ^2.0.4 to allow patch updates, or keep the existing ^2.0 constraint if 2.0.0+ is acceptable.

2. Build Failure Not Addressed

Severity: Critical

According to the PR description, the build failed after this update. The PR should not be merged until:

• The root cause of the test failures is identified
• Code is updated to be compatible with spatie/laravel-model-info v2.0.4
• All tests pass
• The version constraint is changed from pinned to semantic versioning

As the Depfu bot correctly states: "Please do not merge it as is"

---

Code Quality Review

Formatting Changes

The diff shows that the entire composer.json was reformatted from 4-space indentation to 2-space indentation. While this is cosmetic, it:

• Follows JSON standard conventions (2-space indentation)
• Creates a large diff that obscures the actual dependency change
• May indicate the file was manually edited or reformatted by a tool

Note: The repository does not appear to have a .editorconfig or documented formatting standard for composer.json, so this change may be unintentional.

---

Security Concerns

None identified. This is a development/build-time dependency update with no direct security implications.

---

Performance Considerations

None identified. The spatie/laravel-model-info package is typically used during development/debugging and does not affect runtime performance.

---

Test Coverage

Status: Unknown/Failing

The PR description indicates that tests are failing, but the specific failures are not shown. Before this can be merged:

Required Actions:

• Investigate which tests are failing
• Review the changelog for spatie/laravel-model-info v2.0.0-2.0.4 to identify breaking changes
• Update code to address any API changes or deprecations
• Ensure all existing tests pass
• Consider adding tests if new functionality from v2.0 is being used

Areas to Check:
Based on the package purpose (Laravel model information), likely areas of incompatibility:

• Model introspection code
• Commands that use model info (like urls:doctor)
• Any code that directly uses the spatie/laravel-model-info API

---

Recommendations

Required Before Merge:

1. DO NOT MERGE this PR in its current state
2. Investigate the test failures and review the changelog for breaking changes
3. Update code to fix compatibility issues
4. Change version constraint from 2.0.4 to ^2.0.4 or ^2.0 to follow semantic versioning
5. Ensure all tests pass
6. Consider whether the indentation change to composer.json should be kept or reverted

Optional Improvements:

• Add .editorconfig to define consistent formatting standards for the project
• Review other dependencies for similar pinning issues (all others appear to use proper semantic versioning)

---

Conclusion

This PR should not be merged until the build failures are resolved and the version constraint is corrected to use semantic versioning instead of a pinned version. The purpose of this Depfu PR is to alert you to a potential compatibility issue with spatie/laravel-model-info v2.0.4 that needs investigation.