Closed prodrigestivill closed 11 months ago
Started test build 65771
Build 65771 successful To test this build, install it from the testing repository:
flatpak install --user https://dl.flathub.org/build-repo/48412/org.zaproxy.ZAP.flatpakref
Not that I disagree, I have no problem moving to 17. But active support ends in a little over two weeks, security support continues for three years: https://endoflife.date/java
Thanks for this PR! However we should not move to Java 17 until we have a new ZAP release. Java 17 does not include Nashorn, and the current version of ZAP has some problems with GraalJS which is the replacement we are suing. The next version of ZAP should fix these problems so we can update to Java 17 then.
Started test build 65779
ok, no problem. Just removed OpenJDK update.
Build 65779 successful To test this build, install it from the testing repository:
flatpak install --user https://dl.flathub.org/build-repo/48420/org.zaproxy.ZAP.flatpakref
Started test build 65810
Build 65810 successful To test this build, install it from the testing repository:
flatpak install --user https://dl.flathub.org/build-repo/48451/org.zaproxy.ZAP.flatpakref
Thank you!
I created this PR to make this changes:
Please let me know if you prefer separated PR, or to add or remove any of the changes for this PR.
Regarding the flathub external checker configuration, the flathub bot will create PR on each new zaproxy release, an option can be configured to automatically merge those PR by changing the file
flathub.json
by something like this:Let me know also if you want me to add this change in this PR.