update psr/http-message ^2.0 & add ext-mbstring & update stefanak-michal/bolt ^5.1 -> ^6.0

[lcp0578]

update psr/http-message ^2.0

[lcp0578]

When I use it for symfony 6.4 it need psr/http-message ^2.0

[stefanak-michal]

Does it need to keep the old version?

[transistive]

I'd say so yes to maintain backwards compatibility

[stefanak-michal]

your project is php^8 and with the change 1.1 to 2.0 ( php-fig/http-message@1.1...2.0 ) you have nothing to worry about. It's just added argument types and return types.

[transistive]

Thank you for the update! I'll be running some test and merge it later today. Good job!

[lcp0578]

I'm not sureneed to add constraints,

"ext-mbstring": "*"

although Blot already has constraints,
https://github.com/neo4j-php/Bolt/blob/master/composer.json#L12
but when I require this libraries, composer didn't tell me that I needed mbstring extensions, which really wasted a lot of my time, and I found out through debugging that I really didn't have it, but it's not so intuitive, and I hope it will reduce the time of other people who use this library.

[lcp0578]

I think
"php": "^8.0",
https://github.com/neo4j-php/neo4j-php-client/blob/main/composer.json#L24
so,

https://github.com/neo4j-php/Bolt/releases/tag/v6.0.0

I'd like PHP's version constraints to be consistent.

[stefanak-michal]

If you are updating more than psr/http-message you should update PR name.

[lcp0578]

If you are updating more than psr/http-message you should update PR name.

I update the PR name, thx.

[lcp0578]

@transistive If you have time to deal with this PR, my team and I urgently need to update a version.