Discussed this on the meeting. Current idea is to create GH action workflow in keycloak-web, which will:

• Update the keycloak-client version in pom.xml. See some details about this in separate issue Make sure keycloak-web is updated automatically after keycloak-client release keycloak#34666
• Send the blogpost, which will collect the issues fixed in keycloak-client in the particular release and create blogpost from them similar to the Keycloak server blogpost. See for example: https://www.keycloak.org/2024/11/keycloak-2605-released

For now, we may not have "Release notes" and "Upgrading guide" for the keycloak-client, so we can just list the issues (So that is simpler than what is needed for keycloak server ATM).

The workflow can be triggered manually for now after the particular version of keycloak-client is released (We can consider to have it automated, but that might be some next step in the future if needed).