upgrade to v25.0.0 + aggregation of all my PRs
closes #62, #64, #47, #45, #89
special thanks to @waynemorphic who has helped us with some of the v25.0.0 upgrades
@lukin ready for review
Hey folks!
I really appreciate the effort here to generate email templates as well! How do I start utilizing this? I have a fork of keywind with all of my changes in it, should I merge this commit into my fork or just grab the files for the email theme because I dont want it to change what I have customized for my login theme already?
Hi @LeftoversTodayAppAdmin, normally we would have to wait until its merged and you can then pull from origin to your fork.
@lukin do you have any kind of updates for us?
@paulwer thanks for your huge effort!
I am also very interested in creating the mail theming via keywind and would be very happy if we had an ETA for it @lukin
I am currently thinking about forking this repo, and develop it further seperatly, because there has not been any kind of responses for a long time now.
@lukin
I apologize for the long wait for my response. You've done an incredible job and I'm happy with most of the changes. As I wrote earlier, I'm unsure about adding the Mailwind dependency, which is not actively supported. Maybe Maizzle is more suited to the project, but unfortunately, I don't have time to adapt that yet.
Hmm, could we atleast create a PR for updates for keycloak v25? The PR scope could be smaller.
Sure. It will be much easier to merge this without checking the other things. 🙂
Great to hear that <3 I can create an PR without the mail part for now :)
@lukin done, i removed the pr for emails from this pr.
feel free to reach out to me as you like
@lukin i changed the code according to the review.
@lukin any updates?
I am really hoping the maintainer has some time to review the code. It is unfortunate that project seems at a weird state currently, where there are active forks, but the upstream is the blocker.. Probably will have to create my own fork if updates for newer KC versions are not merged by the end of the year. Just throwing it out there, but maybe it is a time to think about more maintainers?
We descided to not support any future updates of this PR due to inactivity. You may want to checkout further informations why we did this here: #108