Fix bazel 9 compatibility: * Update google_cloud_cpp to 3.3.0 to avoid an incompatible version of rules_foreign_cc which uses removed `--incompatible_use_toolchain_transition` * Force rules_go@0.60.0: even google_cloud_cpp@3.3.0 brings rules_go@0.58.3 which is still incompatible with bazel 9. * Update xz to 5.4.5.bcr.8 to avoid having to specify `--incompatible_disallow_empty_glob=false` (in bazel 8 and 9). * Update brotli, bzip2, and snappy, because old versions use `cc_library` or `cc_binary` as builtins which are no longer supported. * Actually update all other dependencies to their current versions. Some of them were already newer due to indirect dependencies, with warnings. Except for abseil-py: on my machine 2.4.0 is broken (cannot find "<Python.h>", in bazel 8 and 9). * Add 3.13 to supported Python versions. Building with `--copt=-Wa,--gsframe=no --host_copt=-Wa,--gsframe=no` might still be needed (in bazel 8 and 9) because of issues in Abseil which were not fixed yet. PiperOrigin-RevId: 903936571
Riegeli/records is a file format for storing a sequence of string records, typically serialized protocol buffers. It supports dense compression, fast decoding, seeking, detection and optional skipping of data corruption, filtering of proto message fields for even faster decoding, and parallel encoding.
See documentation.
Riegeli file format will only change in a backward compatible way (i.e. future readers will understand current files, but current readers might not understand files using future features).
Riegeli C++ API might change in incompatible ways.