[1.x] Constrain Ziggy version to ^0.9.4#395
Merged
taylorotwell merged 1 commit intolaravel:1.xfrom Oct 26, 2020
bakerkretzmar:specify-ziggy-version
Merged
[1.x] Constrain Ziggy version to ^0.9.4#395taylorotwell merged 1 commit intolaravel:1.xfrom bakerkretzmar:specify-ziggy-version
taylorotwell merged 1 commit intolaravel:1.xfrom
bakerkretzmar:specify-ziggy-version
Conversation
bakerkretzmar
changed the title
driesvints
changed the title
driesvints
changed the title
driesvints
changed the title
Member
|
Whoops |
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
3 participants
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.
Related to #392, this PR ensures that Jetstream v1 will install Ziggy
^0.9.4(current as of today), not Ziggy v1.@mattstauffer pointed out that if a user adds Jetstream to their project now but doesn't run the
installcommand for a month, they'll get Ziggy v1 which isn't compatible with Jetstream v1. Adding this version constraint will prevent that.