You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The reason will be displayed to describe this comment to others. Learn more.
@danharrin, why is league/csv being pinned to the exact 9.11.0 release, rather than ^9.11?
9.11 was released on September 23 and there have been three further releases since then. This locks anyone using league/csv on a project with Filament to that specific version.
EDIT: Found #10002 which is the reason for this being introduced.
The reason will be displayed to describe this comment to others. Learn more.
I'll move this discussion to #10002, I'm not familiar with the issue that caused it to be pinned, but a quick look suggests this may need to be fixed in Filament.
829e288
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.
@danharrin, why is league/csv being pinned to the exact
9.11.0
release, rather than^9.11
?9.11 was released on September 23 and there have been three further releases since then. This locks anyone using league/csv on a project with Filament to that specific version.
EDIT: Found #10002 which is the reason for this being introduced.
829e288
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.
If you can confirm that the issue was since fixed, then we can unlock it
829e288
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'll move this discussion to #10002, I'm not familiar with the issue that caused it to be pinned, but a quick look suggests this may need to be fixed in Filament.