v4.3.2 missing binaries?
For the latest release tagged to 4.3.2 there are no platform specific binaries available.
Request to download using latest tag fails: https://github.com/zitadel/zitadel/releases/latest/download/zitadel-linux-amd64.tar.gz
8 Replies
Hi @ghostintown, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Answer
I wasn't able to find a direct answer, here are some relevant sources:
1. Deploy ZITADEL | ZITADEL Docs (1) : This provides information about ZITADEL container images and deployment options, noting that ZITADEL provides stable and latest container images.
2. Release Cycle (2) : This explains ZITADEL's three-month major release cycle and how they handle updates and releases.
For specific issues with missing binaries for v4.3.2, you may want to click the "Ask for help" button to tag a team member who can investigate the release artifacts availability.
To learn more, see the sources I considered:
[1] Deploy ZITADEL | ZITADEL Docs
[2] Release Cycle
Feel free to tag @Ask Inkeep with additional questions.
I would stick with 4.3.1 for the time being, at least the docker images have an invalid css reference making the login page lack styling. im guessing they pulled the binaries for that
I don't have that as an option as the automation script I rely on installs zitadel onto my linux directly through the link I shared above. For time being they could tag 4.3.1 release with latest until the issues are resolved. Or may be hold off new release altogether. But current situation certainly not helping folks relying on automation scripts.
Got it. Tagging @Rajat for additional help.
hey @ghostintown welcome to the server and apologies for the inconviniences, let me look into it 🙂
@Rajat thanks. i see today v4.3.3 is released and that too does not have any binaries published. Could you please share info on why binaries are not provided in last 2 releases and what are your future plans for it?
hey @ghostintown it was not intentional. We just merged a very large DevX PR that replaced the old Makefile‑based build with an Nx monorepo build system. This change broke the release pipeline for patch releases.
I hope this helps 🙂
GitHub
chore: rehaul DevX by eliobischof · Pull Request #10571 · zitadel...
Which Problems Are Solved
Replaces Turbo by Nx and lays the foundation for the next CI improvements. It enables using Nx Cloud to speed the up the pipelines that affect any node package.
It streaml...
@Rajat thanks for getting back with above information. Since, now we know the root cause, when are you expecting new releases (even the minor ones) come with binaries? I see another new release with missed binaries today.