Ah I see. I’ve gotten into some back and forth with the maintainer of Caddy about these build inconsistencies and lack of versioning, and he responded by locking issues on me… twice.
After that communication, I resigned to just keep things as they are because upstream is not willing to make the experience better for use cases like these.
He is impossible to work with, but Caddy is just really good :/
What issue did you have? If I can handle it for the user automatically, I can add a best effort attempt to avoid it.
Just a build conflict, it was resolved upstream in a day or so:
Ah I see. I’ve gotten into some back and forth with the maintainer of Caddy about these build inconsistencies and lack of versioning, and he responded by locking issues on me… twice.
After that communication, I resigned to just keep things as they are because upstream is not willing to make the experience better for use cases like these.
He is impossible to work with, but Caddy is just really good :/