Hmm, interesting... Why is that? :) I will check now
Umm that's bad.. can we switch to a previous release in the meantime ?
I'd suggest yes. The Composer definition tells it to pull in the current master branch, which looking at it is working towards 2.0 right now (major version, B/C break expected). Is there a reason the 1.3.2 tag wouldn't work for us?
1.3.2 tag should work
Updated Composer to use 1.3.2 tag, the rest of the dependencies with updates were processed also. Server updated. Hopefully, we're good to go.
Testing - fixed :)
You may blame the J!Tracker Application for transmitting this comment.
Title |
|
||||||
Status | New | ⇒ | Closed | ||||
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2014-03-27 06:51:17 |
Yeap the same for me... @mbabker check the logs plz :)
You may blame the J!Tracker Application for transmitting this comment.