translatenix

The only failing CI build is check-patch-file. Not sure what to do about this.

Sounds cumbersome. Is this the reason why Pkl's dependencies are so outdated? I was planning to send a couple of PRs that gradually update all of Pkl's dependencies. However, fixing...

@bioball How can we move forward with updating Pkl's dependencies and keeping them up-to-date? Are you aware of a legitimate reason why Pkl's native build still uses JDK11/GraalVM22? If not,...

Is the problem related to newer Truffle library versions requiring Java 17? What's the status of moving to JDK 17? Do users that are still on JDK 11 really need...

Rebased and patch updated. Local build with JDK 21 succeeds. Ready to merge from my side.

> If you can figure out why the hashes changed Test package zip files are created with Gradle's Zip task, so perhaps something changed there. (I think it would be...

@bioball done

@StefMa What’s the benefit? It’s quite verbose.

Doesn’t sound compelling. I think the real benefit is automatic dependency tracking for tasks with `Property` inputs/outputs. Perhaps refactoring the existing code could eliminate a ‘dependsOn’ here and there.

> Hm? This option is meant for debugging, but I put it back. (At some point it didn't work.) > I think we should try to do the "right thing"...