Skip to content

Conversation

@m1ga
Copy link
Contributor

@m1ga m1ga commented Jul 20, 2025

Changes:

Support for Java 24
GraalVM Native Image selection for toolchains
Skipped tests now report assumption violations
Build authoring improvements
Configuration cache improvements

Many changes are just:
old syntax: ndkVersion project.ext.tiNdkVersion
new syntax: ndkVersion = project.ext.tiNdkVersion

  • ✔️ Building the SDK works fine now (one doLast exec deprecation is still shown)
  • ✔️ Building apps works fine now
  • ✔️ building modules works fine (tested a java and kotlin module)

@m1ga m1ga changed the title feat(android): update gradle to 8.14 feat(android): update gradle to 8.14.3 Jul 20, 2025
@m1ga
Copy link
Contributor Author

m1ga commented Aug 14, 2025

Updated the PR.
Only two warnings left when compiling a module:

[INFO]  [GRADLE] > Configure project :module
[INFO]  [GRADLE] The StartParameter.isConfigurationCacheRequested property has been deprecated. This is scheduled to be removed in Gradle 10.0. Please use 'configurationCache.requested' property on 'BuildFeatures' service instead. Consult the upgrading guide for further information: https://docs.gradle.org/8.14.3/userguide/upgrading_version_8.html#deprecated_startparameter_is_configuration_cache_requested
[INFO]  [GRADLE]        at build_4qpbwxslnuklt97pytnq3oqhh.run(/home/miga/dev/ti.animation/android/build/module/build.gradle:4)
[INFO]  [GRADLE]        (Run with --stacktrace to get the full stack trace of this deprecation warning.)
[INFO]  [GRADLE] The Configuration.fileCollection(Spec) method has been deprecated. This is scheduled to be removed in Gradle 9.0. Use Configuration.getIncoming().artifactView(Action) with a componentFilter instead. Consult the upgrading guide for further information: https://docs.gradle.org/8.14.3/userguide/upgrading_version_8.html#deprecate_filtered_configuration_file_and_filecollection_methods

sadly I can't find where they are :-( But the first one is for gradle 10 so we have more time to fix that one

@m1ga
Copy link
Contributor Author

m1ga commented Oct 1, 2025

Turned out the last warning was a Kotlin related warning. Upgrading the Kotlin version fixed it: https://stackoverflow.com/a/79282059/5193915

@m1ga m1ga marked this pull request as ready for review October 1, 2025 11:35
@m1ga m1ga requested a review from cb1kenobi October 1, 2025 11:37
Copy link
Contributor

@cb1kenobi cb1kenobi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested on Windows 11 and works great!

I should mention that I built the SDK from source and it downloaded the new Gradle version.

@socket-security
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedliveview@​1.5.6721009984100
Addednode-titanium-sdk@​6.1.0771007687100
Addednodeify@​1.0.11001009677100
Addedlodash.merge@​4.6.21001007780100
Addedmarkdown@​0.5.01009310080100
Addedlockfile-lint@​4.14.19910010081100
Addednode-appc@​1.1.7821008781100
Addedmoment@​2.30.11001009183100
Addedmocha@​11.7.4971009595100
Addedlint-staged@​16.2.510010010096100

View full report

@socket-security
Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn Critical
[email protected] has a Critical CVE.

CVE: GHSA-crh6-fp67-6883 xmldom allows multiple root nodes in a DOM (CRITICAL)

Affected versions: <= 0.6.0

Patched version: No patched versions

From: package-lock.jsonnpm/[email protected]npm/[email protected]

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants