Lines Matching +full:pr +full:- +full:dependencies +full:- +full:check

16 As mentioned above, updating to a new Compose snapshot is done by submitting a new PR against the `…
20 # Create branch for PR
21 git checkout -b update_snapshot
35 ./gradlew check
40 Finally create a PR (with the base branch as `snapshot`) and send for review.
54 # Create branch for PR
55 git checkout -b main_snapshot_merge
61 ### #2: Update dependencies
67 1. Update the `composesnapshot` property to a single character (usually `-`). This disables the sna…
68 2. Update the `compose` property to match the new release (i.e. `1.0.0-beta06`)
72 ./gradlew check
81  * Update the `VERSION_NAME` property and remove the `-SNAPSHOT` suffix.
87 Push the branch to GitHub and create a PR against the `main` branch, and send for review. Once appr…
91 Once the above PR has been approved and merged, we need to create the GitHub release:
96  * Double check everything, then press 'Publish release'.
98 At this point the release is published. This will trigger the docs action to run, which will auto-d…
106 …* Update the `VERSION_NAME` property, by increasing the version number, and adding the `-SNAPSHOT`…
107  * Example: released version: `0.3.0`. Update to `0.3.1-SNAPSHOT`