Skip to content
KilogentLog inContact salesStart free

One site, one publisher

Kilogent team

This site used to live inside the application monorepo. It does not any more.

The failure that decided it

Two repositories publishing one hosting target is last-writer-wins with no error. The tooling publishes whichever ran most recently and exits successfully — so an older build silently replaces a newer one, and nothing anywhere reports it.

The fix is structural rather than procedural: one site, one publisher.

Try it with your team

Describe one goal. Kilogent proposes the agents. Nothing runs until you say yes.

More from the blog