From c3861819bc41b0bc47c943577ac0e30234707df7 Mon Sep 17 00:00:00 2001 From: Christian Blichmann Date: Fri, 10 Jul 2020 02:49:38 -0700 Subject: [PATCH] Update Hello SAPI's WORKSPACE for newer Bazel versions Bazel 3.x now requires specifying `commit`, `tag` or `branch` in its `git_repository` rule. PiperOrigin-RevId: 320572176 Change-Id: I81048d997f595202f4dfbd3c1e9c8321240a28a3 --- sandboxed_api/examples/hello_sapi/WORKSPACE.bazel | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/sandboxed_api/examples/hello_sapi/WORKSPACE.bazel b/sandboxed_api/examples/hello_sapi/WORKSPACE.bazel index cf7455e..145428f 100644 --- a/sandboxed_api/examples/hello_sapi/WORKSPACE.bazel +++ b/sandboxed_api/examples/hello_sapi/WORKSPACE.bazel @@ -27,8 +27,9 @@ maybe( git_repository, name = "com_google_sandboxed_api", # This example depends on the latest master. In an embedding project, it - # is advisable to pin Sandboxed API to a specific version. + # is advisable to pin Sandboxed API to a specific revision instead. # commit = "ba47adc21d4c9bc316f3c7c32b0faaef952c111e", # 2020-05-15 + branch = "master", remote = "https://github.com/google/sandboxed-api.git", )