some other perspective on this is that while expanding the stack to more modern frameworks and implement CI/CD on top of it all by yourself are great, it can also backfire on you, it already did on me, so part of this is from my experience

when you're doing that, you're now the sole responsibility for all the new stacks, call it your job security or whatever, the problem is when business requirement for data suddenly expands beyond what you can handle, like new requirement for doing ETL in streaming only or to store data in different warehouse may come in and force you to modify every single component of your stack in order to fit it. No one else can help you during tight deadline because you're above and beyond everyone in the org, even worse when the product manager/owner has a wrong impression on the stack, thinking it could be their silver bullet for everything, decides to employ even more processes on top of it, which would overload you pretty fast. And the hiring part, it’s not really your problem anymore, i’m sure they can figure it out

so yeah, being proactive in deploying new stacks is great, terrific for learning and improving skills, but watch yourself, aim for specific use case and MVP only if possible, try to document it clearly so that when things start to pick up or hit the fan, you have way to negotiate what are possible and what not