New tools are always like this: the good parts are amazing, but the unfinished parts can be a headache. Recently, I tried to set up an automated build system using pixi and rattler‑build to regularly package and upload opencode to prefix.dev. The whole process took about 6 hours, during which I encountered quite a few unexpected issues.

As the number of projects I need to maintain keeps growing (3 official websites, 2 systems, and 1 mini‑program, all with separate front‑end/back‑end and independent databases), I’ve encountered many tasks that are trivial to do once but become chaotic when repeated many times across different contexts. I had already experimented with CI on GitHub, and this time I learned and practiced CD (Continuous Deployment).

In CI/CD workflows, dependency management is often a key factor determining build efficiency and reliability. Recently, I tried the setup-pixi GitHub Action in a static website deployment pipeline.