Simon Berger

Indeed a "rolling update" via deprecation is not really necessary for new major releases. Regarding the change in v3 beside the missing upgrade note my main concern was the lack...

It should be `int|string` (from the possible parameters I know (`hash, salt...`). Maybe there are even more). This describes every possible single parameter, not all together.

This feature seem not to be planned anymore? I tested the solution @hallboav provided, it works good, thank you for that. Unfortunately it has yet two flaws which makes it...

> > for a relatively neat technology like JWT which could be unmaintained in the future. > > ???????????? What? Where exactly is your big question mark? I was talking...

Firstly I wait as well for a fixed release of this extension compatible with PHP 8.3. Still this PR is not needed and just causes confusion. It should be closed...

@nicodemuz I just came just came along to look for this bug. Is this indeed fixed in one of the most recent commits? `2.1.0` still has this issue and I...

Were there any new insights or had this been closed due to inactivity? I have this error as well after executing unit tests with codeception. PHP 8.3 and protobuf extension...

There is a new issue with a simple reproducer and a PR with a fix. Unfortunately both without any reaction yet. I expect most of you reported the issue here...

Please describe the options you used. The width is far too wide to be rendered on a normal page in default settings.

I can confirm the behavior in v0.7.0 and master. You can fix this behavior if you add a ```page-break-after: always``` to ```.page``` This still adds an empty page at the...