Update dependencies and improve workflow docs (#3071)

- Relaxed Google Cloud and gRPC upper bounds to dynamic versions in dependencies.gradle.
- Relaxed JUnit testing framework bounds to < 6.0.0 and < 2.0.0.
- Aligned beam-runners-core-construction-java to 2.72.0!!
- Regenerated all gradle lockfiles across the project.
- Updated GEMINI.md and MEMORY.md with the optimized lockfile/dependency update workflow.
- Fixed presubmit errors in check_diff.py (added Apache 2.0 license header and fixed syntax).
This commit is contained in:
Ben McIlwain
2026-05-28 21:45:43 +00:00
committed by GitHub
parent d68f3e5cc0
commit beb7fcc16e
11 changed files with 508 additions and 363 deletions
+5
View File
@@ -53,6 +53,11 @@ This document outlines foundational mandates, architectural patterns, and projec
### 6. Project Dependencies
- **Common Module:** When using `Clock` or other core utilities in a new or separate module (like `load-testing`), ensure `implementation project(':common')` is added to the module's `build.gradle`.
- **Updating Dependencies:** When updating third-party dependencies, you must follow this exact sequence:
1. Modify `dependencies.gradle`.
2. Run `./gradlew dependencies --write-locks` to regenerate the Gradle lockfiles locally. This is much faster than running the full update script blindly.
3. Verify the build succeeds (e.g., `./gradlew :core:build -x test` or `./gradlew build`) to ensure there are no resolution or compilation errors.
4. ONLY after the lockfiles are generated and the build is verified, execute the internal script `/google/src/head/depot/google3/domain/registry/tools/update_dependency.sh` to push the new dependencies to the private Maven repository.
### 7. Search and Discovery
- **No CodeSearch:** This project is hosted on GitHub, not Google3. Do NOT use `mcp_Coding_search_for_files_codesearch` or other internal Google3 search tools.