Release of version 1.1.0 is actually version 2 about laravel-event-sourcing HOT 7 CLOSED

I'll take care of this soon!

from laravel-event-sourcing.

Done!

from laravel-event-sourcing.

Just to make it easier, here with links:
Tag 1.1.0 points to commit f72358f

from laravel-event-sourcing.

I am going to piggyback off this issue, because I believe it is closely related.

This is what happens when adding the library to my project, which causes a fatal error during package:discover.

$ composer require spatie/laravel-event-sourcing
Using version ^1.0 for spatie/laravel-event-sourcing

If I attempt to explicitly call the v3.0, I receive errors about not meeting library requirements.

$ composer require spatie/laravel-event-sourcing:^3.0
 Package spatie/laravel-event-sourcing at version ^3.0 has a PHP requirement incompatible with your PHP version (7.3) 

However, the version of PHP I am running passes the documented requirements:

PHP 7.3.14 (cli) (built: Feb 1 2020 20:48:29) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.14, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.14, Copyright (c) 1999-2018, by Zend Technologies

from laravel-event-sourcing.

This package has required PHP 7.4 from version 1.1.0, which you can see in composer.json

The requirements weren't updated in the docs correctly, I've fixed that now

from laravel-event-sourcing.

@riasvdv Thank for updating the docs, but I think, this didn't address the problem.

My point is: v1.1.0 is tagging the wrong commit. As outlined above, the actual changelog for v1.1.0 is here: https://github.com/spatie/laravel-event-sourcing/blob/v1/CHANGELOG.md#110---2020-02-07. Compare this to the changelog of the tree of the tagged commit: https://github.com/spatie/laravel-event-sourcing/blob/f72358f0357d8bee7882b94b767cd26a1e160117/CHANGELOG.md

I recommend to drop the v1.1.0 tag, and create a new v1.1.1 to this commit: 851f7e6

from laravel-event-sourcing.

Thank you!

from laravel-event-sourcing.