Allow doctrine/persistence 4.0

[fmata]

No description provided.

[reubensant]

Shall this be merged any time soon, please?

Can no longer use master JWTRefreshTokenBundle with Symfony LTS 6.4.21 - a new project installs doctrine/persistence 4

gesdinet/jwt-refresh-token-bundle[v1.1.2, ..., v1.4.0] require doctrine/persistence ^1.3.3|^2.0|^3.0 -> found doctrine/persistence[1.3.3, ..., 1.3.8, 2.0.0, ..., 2.5.7, 3.0.0, ..., 3.4.0] but the package is fixed to 4.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

[andrec93p]

We also need this. Can you please merge?

[shkabo]

@mbabker can we get this merged ? Thanks :)

[mbabker]

@mbabker can we get this merged ? Thanks :)

I don't have merge rights to this repo otherwise it'd be done already.

[shkabo]

@mbabker unlucky. Sorry for pinging you then :/

@markitosgv can we get this merged? Thanks :)

[reubensant]

Could anyone please suggest a workaround or alternative approach until this is merged?

I’d like to continue using this bundle with the latest Symfony LTS, specifically with persistence 4, preferably without having to fork the project.

[andrec93p]

Could anyone please suggest a workaround or alternative approach until this is merged?

I’d like to continue using this bundle with the latest Symfony LTS, specifically with persistence 4, preferably without having to fork the project.

I'm personally not aware of any, but if anybody finds something I'd like to know too.

[lolmx]

@reubensant @andrec93p

// composer.json

"require": {
  "gesdinet/jwt-refresh-token-bundle": "dev-feature/doctrine-persistence-4",
},
"repositories": {
  "fmata_jwtrefreshtokenbundle": {
    "type": "vcs",
    "url": "[email protected]:fmata/JWTRefreshTokenBundle.git"
},

then you can run composer update gesdinet/jwt-refresh-token-bundle