translatenix

Another observation is that out of 46 stale output files, 44 have the extension `.pcf`.

Unfortunately I can't reproduce locally. Is it possible to trigger PR builds automatically for contributors? Otherwise the feedback loop is too long.

I found and fixed the problem. It wasn't showing locally because the test was using cache dir ~/.pkl/cache. The fix makes breaking changes to spi.v1, which probably isn't a good...

@holzensp @bioball I think I've addressed all feedback (see recent commits) except for the following open questions: 1. `pkl-certs` details (see that thread) 2. `org.pkl.executor.Executor` details (see that thread) 3....

@holzensp @bioball I'm blocked on your feedback. I'd love to land this PR and #227 ASAP to stabilize the build/tests. It will make everything easier for everyone. > I think...

I've now implemented spi.v2 to support certificate files (and `testPort` in #227 ) without introducing breaking changes. I've also made sure that pkl-certs gets published. This is ready to be...

I've addressed everything I could in my latest commit (as per my comments). Once you're ready to merge, please squash before merging (or ask me to squash).

Instead of backing out all SPI changes, I switched to your suggested implementation approach. To gain some confidence in this approach, I massively improved `EmbeddedExecutorTest`. Details in the commit message....

Which aspect of snapshot versions are you interested in? Easy update to the latest version for package consumers, or something else?

Personally I'm more interested in the consumer side. For the producer, it seems OK to publish a normal release every time.