Laravel Version: 5.5.28+
PHP Version: n/a
Database Driver & Version: n/a
The is basically the same issue as #22462. The framework is currently at 5.5.31, yet individual packages are behind.
Is this on purpose or a mistake in your release procedure or release-script(s)?
In any case, I hope that you can take a good look at this issue, because I fear that important (security) updates might not get pushed through to the individual packages, when in fact they might be available in the framework.
I've asked about this before, and they always seem to ignore the issue. Would like to know why this happens as well 👍
Is anyone of the core team look at this?
While waiting for a reply or action to be taken, I guess the only solution (workaround) is to use the entire framework. Thus far I haven't seen nor felt any security issues, but this does somewhat keep me up at night!
@themsaid?
Working on an automated tool that’ll take care of that from now on.
Will release all components today, sorry guys 🙂
Sent from my iPhone
On Jan 30, 2018, at 10:16 AM, Nat Zimmermann notifications@github.com wrote:
@themsaid?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Thanks for the update!
@themsaid JFYI maybe this tool could help : https://github.com/fabpot/gitter
Most helpful comment
Working on an automated tool that’ll take care of that from now on.
Will release all components today, sorry guys 🙂
Sent from my iPhone