protobuf

17735 Commits

201 Branches

346 Tags

254 MiB

Tag: Branch: Tree: 81041edfae

Commit Graph

Author SHA1 Message Date

Author	SHA1	Message	Date
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

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

2 Commits (81041edfaea0f9ff7f724a0079542abd544f62e4)