Please tag a new release with SF8 support (PR #109 merged, PR #111 pending)

[jjbier]

Context

PR #109 ("Add Symfony 8 support") was merged on 2026-03-25 into master. However, no new release has been tagged since then — the latest release is still 3.1.0 (which only declares symfony/framework-bundle: "^6.4 || ^7").

We are currently running a Symfony 7.4 → 8.0 migration and need an installable release that declares ^8.0 support so we can use standard composer require instead of a VCS override.

Blocker: PR #111 should be merged first

PR #111 ("fix: remove deprecated eraseCredentials() — breaks logout on Symfony 8") is currently open and targets a real regression introduced by the SF8 merge: calling $security->getToken()?->eraseCredentials() in the Logout controller is fatal on Symfony 8.0 since eraseCredentials() was removed from UserInterface. This must be merged before tagging a release that declares SF8 support — otherwise logout is broken for all SF8 users.

Request

1. Merge PR fix: remove deprecated eraseCredentials() — breaks logout on Symfony 8 #111 into master.
2. Tag a new release (e.g., 3.2.0) that includes both Add Symfony 8 support #109 and fix: remove deprecated eraseCredentials() — breaks logout on Symfony 8 #111.

Workaround we are using in the meantime

We have forked the repository, applied PR #111 on top of master, and are pointing our composer.json to our fork via a VCS repository entry. We will switch back to the official package as soon as a release is available.

Thank you for maintaining this bundle!

[drupol]

Hello,

Thanks for the heads up!

What would be the best way to handle the issue at hand? Do you have some hints on how to fix this gracefully ?

[smbpunt]

I've updated the PR in order to

fix this gracefully