-
-
Notifications
You must be signed in to change notification settings - Fork 261
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
80c2b29
commit 0e8a437
Showing
1 changed file
with
3 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
0e8a437
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DavidBadura something is wrong here. packagist is not seeing the 1.0.2 release, and the changelog seems wrong?
v1.0.1...v1.0.2
Looks like #250 was fixed in 1.2.0
0e8a437
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I should have solved the problem with packagist.
I don't understand you. We don't have a release/branch named 1.2.0. The master will be version 2.0.
But #250 was merged into 1.0 branch and i have created the tag v1.0.2 there. Did I do something wrong?
0e8a437
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, #250 was fixed in 1.0.2 but it's under 1.0.1 in the change log. that's all. (i mistyped 1.0.2 as 1.2.0)
Thanks!