)]}'
{
  "commit": "93262a5b1eb7bb898ebaf6cf0466ad1c1beb1d6f",
  "tree": "9e54f7be61c614791c7b150467dbf67a60129a86",
  "parents": [
    "5e486a2bb2a79afa73f7b7fda53c320bb2930b96"
  ],
  "author": {
    "name": "Bazel Release System",
    "email": "noreply@google.com",
    "time": "Mon Jul 13 17:23:50 2020 +0200"
  },
  "committer": {
    "name": "Tobias Werth",
    "email": "twerth@google.com",
    "time": "Mon Jul 13 17:23:50 2020 +0200"
  },
  "message": "Release 3.4.0 (2020-07-13)\n\nBaseline: 7404d17ac76da876ae0b432d1fccf222a9e991fe\n\nCherry picks:\n\n   + a4334be50a206bf8d676a0196af11056c48ac35b:\n     fixup! Gracefully handle the lack of subreaper support in Linux.\n\nIncompatible changes:\n\n  - This removes the short-lived --process_wrapper_extra_flags\n    flag, which was introduced primarily to roll out a bug fix.\n    Unfortunately,\n    this made us inadvertently expose all of the process-wrapper\u0027s\n    command line\n    interface to the public, which should not have happened.  Given\n    the corner\n    case of the utility of this flag, the lack of documentation for\n    it, and the\n    fact that it only appeared in a single release, we are treating\n    this as a\n    bug instead of a backwards compatibility breakage.\n\nNew features:\n\n  - bazel info: Allow to specify multiple keys.\n  - Support code coverage with GCC 9.\n\nImportant changes:\n\n  - Allow InstrumentedFilesInfo fields to be read from Starlark.\n  - The --starlark_cpu_profile\u003d\u003cfile\u003e flag writes a profile in\n    pprof format containing a statistical summary of CPU usage\n    by all Starlark execution during the bazel command. Use it\n    to identify slow Starlark functions in loading and analysis.\n  - The --debug_depset_flag has been removed as it is in effect\n    always on at no cost.\n  - Rule authors should use the\n    incompatible_use_toolchain_transition rule attribute to migrate\n    to using\n    the toolchain transition. jcater to udpate notes further.\n  - `apple_binary` rules now accept the `stamp` attribute with the\n    same\n    semantics that it has in `cc_binary` rules.\n  - --incompatible_objc_provider_remove_compile_info turns off\n    the compile info/mege_zip Starlark APIs in ObjcProvider.  See\n    #11359.\n  - The --debug_depset_flag has been removed as it is in effect\n    always on at no cost.\n  - Fix behavior of ctx.actions.write so content is written without\n    an incorrect encoding to UTF-8.\n    See https://github.com/bazelbuild/bazel/issues/10174 for details.\n  - Collect more performance metrics for worker execution.\n  - Add flag --incompatible_force_strict_header_check_from_starlark\n  - Configure coverage and runfiles for sh_library.\n  - Adds --incompatible_blacklisted_protos_requires_proto_info to\n    indicate whether proto_lang_toolchain.blacklisted_protos requires\n    ProtoInfo.\n\nThis release contains contributions from many people at Google, as well as Andrzej Guszak, Benjamin Peterson, Benjamin Romano, Carlos Eduardo Seo, Claudio Bley, dannysullivan, David Ostrovsky, George Gensure, Graham Jenson, Grzegorz Lukasik, Gunnar Wagenknecht, Henk van der Laan, Jin, John Millikin, Marin Baron, Nikhil Marathe, Robin Nabel, Ryan Beasley, Samuel Giddins, Sergey Balabanov, utsav-dbx, Vo Van Nghia, Yannic Bonenberger.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "20db4843e027062a8d62464870d4078b59db7045",
      "old_mode": 33188,
      "old_path": "CHANGELOG.md",
      "new_id": "e5d6ecc9fa59309429886f7045927f41e22f4fc1",
      "new_mode": 33188,
      "new_path": "CHANGELOG.md"
    }
  ]
}