Skip to content

Conversation

@ahus1
Copy link
Contributor

@ahus1 ahus1 commented Jun 11, 2024

Closes #30351

@ahus1
Copy link
Contributor Author

ahus1 commented Jun 12, 2024

@mhajas - The tests are green, and I tested locally that the migration is called upon migration when a new version of Keycloak starts up.

Please give it a review when you have the time. I plan to do a backport to KC25 once this is merged. Thanks!

@ahus1 ahus1 requested a review from mhajas June 12, 2024 07:33
Copy link
Contributor

@mhajas mhajas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the fix. It makes sense to me, however, I am not sure it makes sense to merge this fix to main, since this code will be removed in 26. We can send the PR only to 25. But still I am approving and leave it to you whether we want to merge or no.

@ahus1 ahus1 merged commit a161827 into keycloak:main Jun 12, 2024
@ahus1
Copy link
Contributor Author

ahus1 commented Jun 12, 2024

I'm so used to first do things in upstream, and then backport them, let's stick to that. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Migration of sessions in KC25 should run only on migration, not on imports

2 participants