Add graddle lockfile update to the documentation #1350
Conversation
larkox
added
1: Dev Review
|
Newest code from larkox has been published to preview environment for Git SHA 7f288c4 |
| We use lockfiles to lock dependencies and make sure the builds are reproductible. If we want to update the lockfile to update all dependencies to the latest, we can run these commands: | ||
| ``` | ||
| cd android | ||
| ./gradlew app:dependencies --update-locks "*:*" |
There was a problem hiding this comment.
What if we dont want the latests but the specific verdions we are using?
There was a problem hiding this comment.
The specific versions we are using would be already in the repo (in the lockfile).
If we want to generate them from the scratch (remove the lock file and regenerate it) we would call ./gradlew app:dependencies --write-locks. Is that what you mean?
There was a problem hiding this comment.
Yes.. cause this is how I envision it.
Add a new dependency to the project or bump dependencies manually, then update the lock.. kind of the same we do with gems, cocoapods and npm
|
Newest code from larkox has been published to preview environment for Git SHA 142aa81 |
cwarnermm
added
4: Reviews Complete
|
Newest code from cwarnermm has been published to preview environment for Git SHA 3eebeb6 |
Summary
We add documentation on how to update the lock files.
This is dependent on mattermost/mattermost-mobile#7875
Ticket Link
NONE