The only part of this process I’d consider automating with a LLM is summarizing the changes, and even then I’d only be interested looking at a suggested changelog, not something fully automated.

It’s amazing to me how far people will go to avoid writing a simple script. Thankfully determinism isn’t a requirement for a release pipeline. You wouldn’t want all of your releases to go smoothly. That would be no fun.

So this is Jenkins except it guzzles water and ruins the lives of people near data centers?

This doesn’t seem like a good idea.

One, releasing should be easy. At my last job, you clicked “new release” or whatever on GitHub. It then listed all the commits for you. If you “need” an Ai to summarize the commits, you fucked up earlier. Write better commit messages. Review the changes. Use your brain (something the AI can’t do) to make sure you actually want all of this to go out. Click the button. GitHub runs checks and you’re done.

Most of the time it took a couple minutes at most to do this process.

this seems overengineered to me - it’s easy enough to have fully automated builds, deployments and releases already. you can even have ai sketch your github actions or similar config. anything beyond that is simply a downgrade or reinventing the wheel. a git commit hook might be just enough