Repository navigation
add support for Laravel 13 - #1
Merged
Merged
Conversation
…ncy version ranges.
Contributor
|
Why do you want to change the package name? |
Contributor
Author
Have you looked into the changes properly? I did change it initially cause I thought of forking and releasing my own version, but later I made a PR on your repo itself, i've only bumped the supported version if you look at the final changes |
Contributor
|
@tapan288 no need to harsh on me :) my bad i was looking into the composer.json file differences. I have approved the PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.