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

Author	SHA1	Message	Date
Sandy Zhang	1a716d6b69	Update BCR presubmit to use C++17 This reflects the new minimum as of v30 per https://engdoc.corp.google.com/eng/doc/devguide/proto/news/2024-10-02.md#drop-cpp-14 PiperOrigin-RevId: 694507579	3 weeks ago
Protobuf Team Bot	56219aa08b	Upgrade rules_java and remove experimental_google_legacy_api flag The upgrade of rules_java also upgrades error prone and this resulted in some additional errors reported in Protobuf's tests. Set the flag to report those as warning, but they should be cleaned up eventually. PiperOrigin-RevId: 687070204	1 month ago
Mike Kruskal	adaec55ffc	Drop bazel 6 in BCR and add --experimental_google_legacy_api for testing PiperOrigin-RevId: 681081216	2 months ago
Sandy Zhang	773e931532	internal change PiperOrigin-RevId: 676549386	2 months ago
Sandy Zhang	b9d1cfff8c	Add protobuf_java to Bzlmod presubmit checks. PiperOrigin-RevId: 661428018	4 months ago
Sandy Zhang	3a79dc7a09	Remove protobuf rust from BCR presubmits for now. Rust protobuf is in development and not intended for use / released yet. We should add this back at some point when rust is ready for release, after adding equivalent GHA presubmit tests. PiperOrigin-RevId: 653252995	5 months ago
Protobuf Team Bot	2eb4d69ed5	Add minimal Python support to MODULE.bazel PiperOrigin-RevId: 642857334	6 months ago
Protobuf Team Bot	f3c140f96c	Add Rust support to MODULE.bazel PiperOrigin-RevId: 640804047	6 months ago
Sandy Zhang	df630fa6f1	MODULE.bazel fixes for protobuf BCR release. - Specifies bazel version for presubmits - Set C++14 version (default is c++11 otherwise, which is unsupported) - Update MODULE.bazel version + updater since publish-to-bcr can't handle constants and adds a duplicate version number PiperOrigin-RevId: 633729225	7 months ago
Alex Eagle	d2b71b347d	feat: automate publishing releases to Bazel Central Registry (#16014 ) Note, recent releases on the BCR have a patch set applied, and it seems these patches are developed independently to "fix" each protobuf release, rather than make changes to protobuf repo. The effect of this PR will be to create a broken publish to BCR for each protobuf release. At least this red PR on BCR will be our indication that the patches need to be manually replayed there. In parallel, starting with #16013 I'll apply as many of those patches to the protobuf repo as possible. That will reduce the manual effort for each release. Replaces https://github.com/protocolbuffers/protobuf/pull/14565 which originated from my fork so the tests wouldn't run. Closes #16014 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/16014 from protocolbuffers:bcr `e17d9c8127` PiperOrigin-RevId: 615026796	9 months ago