Chiebot-Mirror/protobuf - protobuf - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Protobuf Team Bot	6ed0b9f28d	Internal change PiperOrigin-RevId: 670152183	7 months ago
Joshua Haberman	e4449ba248	Harmonize license rules between google3 and OSS This simplifies upb by removing differences between google3 and OSS. This also points upb at the protobuf license, instead of keeping a separate copy around for upb. PiperOrigin-RevId: 669447145	7 months ago
Protobuf Team Bot	182699f8fd	Internal change PiperOrigin-RevId: 667891921	7 months ago
Protobuf Team Bot	9f9cb7a10e	Move proto_toolchain from rules_proto to protobuf The toolchain type is consumed by proto_library and produced by proto_toolchain rule. As such it's a private dependency, because both rules are now part of protobuf repo. There are some early adopters of --incompatible_enable_proto_toolchain_resolution that might be broken from this: grpc, rules_go, rules_ts, rules_rust, rules_lint, because they have implementation that is not using proto_common. Those repositories need to define their own proto_lang_toolchain and consume it with proto_common.compile. PiperOrigin-RevId: 654897871	8 months ago
Protobuf Team Bot	b3c9f4e0a9	Implement proto_lang_toolchain rule Enable the Starlark rule only on Bazel versions, that have the Starlark version of ProtoInfo provider. That's needed, because only that exposed _transitive_proto_info field that's used in the rule. PiperOrigin-RevId: 651753437	9 months ago
Protobuf Team Bot	7a7efe9e64	Add bzl_libraries to protobuf PiperOrigin-RevId: 623784182	12 months ago
Protobuf Team Bot	21d75f861c	Remove references to rules_proto They are not needed after the rules are move into protobuf repo. Except for the reference to toolchain type, which is currently in rules_proto and can be moved after the implementation is moved into protobuf repo. PiperOrigin-RevId: 622176865	12 months ago
Protobuf Team Bot	d4d34abd7d	Add redirects for proto rules Redirected rules: proto_library, proto_toolchain, proto_lang_toolchain Modules and providers: proto_common, ProtoInfo, ProtoLangToolchainInfo The structure follows proposal: https://docs.google.com/document/d/1L1JFgjpZ7SrBinb24DC_5nTIELeYDacikcme-YcA7xs/edit?usp=drive_open&ouid=102306600948089647787 PiperOrigin-RevId: 622117921	12 months ago