3.3.1 & 3.3.2 stubs

Question

nmapx opened this issue 6 years ago · 6 comments

Again, may I ask you to add stubs for those releases?
Maybe you should think about including this step in your release process? 😄

Answer 1 · 2018-03-13T13:21:19.000Z

Agreed. Stubs need to be automatically generated after each release. Not manually anymore.

Answer 2 · 2018-03-15T14:55:25.000Z

Thanks @virgofx. Can you push requested stubs manually in the meantime?

Answer 3 · 2018-03-15T16:10:36.000Z

Answer 4 · 2018-03-21T05:46:35.000Z

There is no API changes as I know for Phalcon 3.3.2. Why do we need to regenerate stubs?

Answer 5 · 2018-03-21T13:14:58.000Z

Just to keep version parity with Phalcon. This repo needs to be built and tagged in an automated fashion when Phalcon releases new version.

Answer 6 · 2018-03-22T09:30:21.000Z

Just released v3.3.1 and v3.3.2