1.4 KiB
1.4 KiB
name | about | title | labels | assignees |
---|---|---|---|---|
Dependency update | Update existing dependency to a new version. | dependencies |
For a Gradle dependency:
- Update the dependency version in the root
gradle.properties
- Update the dependency locks
- For Gradle plugins:
./gradlew dependencies --write-locks
- For Gradle dependencies:
./gradlew resolveAndLockAll --write-locks
- For Gradle plugins:
- Verify no unexpected entries appear in the lockfiles. A supply chain attack could occur during this stage. The lockfile narrows the supply chain attack window to this very moment (as opposed to every time a build occurs)
- Are there any new APIs or possible migrations for this dependency?
For Gradle itself:
- Run
./gradle wrapper --gradle-version $X
- Add
distributionSha256Sum=
ingradle/wrapper/gradle-wrapper.properties
, referencing Gradle Release Checksums - Update the continuous integration server environment variables with the updated SHA for the Gradle wrapper, referencing Gradle Release Checksums. Note: Bitrise builds for other branches may temporarily fail since only a single checksum at a time is currently supported. The wrapper is not updated with every Gradle version so in practice this problem should occur infrequently.
- Are there any new APIs or possible migrations?