jbonofre commented on PR #10485: URL: https://github.com/apache/iceberg/pull/10485#issuecomment-2161023449
Not sure it makes sense to trigger revapi (api compatibility workflow) when gradle or github folders are updated. Can you please provide the rationale here ? The problem with Gradle 8.2+ update is not when revapi is triggered, it's an issue on the revapi gradle plugin itself (see https://github.com/palantir/gradle-revapi/issues/612). I'm working to fix this issue in the plugins (both revapi and shadow) and I have a fallback PR with a `revapi` script. So I don't think it makes sense to change the workflow trigger. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
