Daniel Kudwien

Sorry, I was mistaken - the same code still exists; Git only got confused because the original files were seemingly moved around. Updated the PR for the current version.

The TravisCI failures and errors existed before already and are not related to this PR.

See also https://github.com/usefulteam/jwt-auth/issues/121

The GitHub Action actually failed: https://github.com/usefulteam/jwt-auth/actions/runs/8992257107/job/24701674019 Looking at the log, I think we can additionally exclude some Composer libraries: ``` vendor/guzzlehttp vendor/doctrine vendor/nikic vendor/phar-io vendor/phpunit ``` …though that being said...

Ah that makes sense – so we can just exclude the files you listed originally. Not sure about `trunk` though. The ["New tag" action](https://github.com/usefulteam/jwt-auth/actions/runs/8992257107/job/24701674019) was actually updating the files in...

This seems to be a nice quick fix we could include in the next release.

For the moment it would be best to disable all automated formattings and then revert all changes in this PR that are not functional changes. In an issue separate from...

This is still blocked on backwards compatibility; see https://github.com/usefulteam/jwt-auth/pull/116#discussion_r1967782945

That’s correct; the auth system of WordPress core is not bootstrapped yet in plugins_loaded. You can also see this in the WordPress Action Reference manual page. I don’t really see...

All issues and pull requests linked in the issue summary are closed, so in theory, this epic seems to be resolved. But I'm coming here, because we just started to...