Age | Commit message (Collapse) | Author |
|
Merge release commits to 26.x
|
|
|
|
|
|
Set label to REQUIRED for descriptors with LEGACY_REQUIRED feature.
|
|
to this.features
PiperOrigin-RevId: 619261163
|
|
Update protoc release to include editions language features protos fo…
|
|
Move java_features.proto to java/core/srce/main/resources
|
|
https://github.com/protocolbuffers/protobuf/commit/bca8fb6117cf24785edb238d96bffe2c3a6d7164
|
|
|
|
|
|
|
|
Cherry-pick changes 26.x
|
|
This also fixes maven to package this correctly as google/protobuf/java_features.proto (same dir as WKT/descriptor.proto) instead of com/google/protobuf/java_features.proto.
Fixes https://github.com/protocolbuffers/protobuf/issues/16155
PiperOrigin-RevId: 617307475
|
|
Ensures isOptional() does not return true for LEGACY_REQUIRED fields which would otherwise get the optional label applied by default (non-optional fields still get the optional label).
Adds validation to feature resolution instead of cross link, which is too early to have FieldPresence.LEGACY_REQUIRED resolved.
PiperOrigin-RevId: 618857590
|
|
and C++
Fixes https://github.com/protocolbuffers/protobuf/issues/16211
PiperOrigin-RevId: 618954029
|
|
PiperOrigin-RevId: 618295219
|
|
When using bazel platforms and new rules_android_ndk, crosstool_top is actually still `//external:android/crosstool`. The right way to detect Android is to use `constraint_value`.
Closes #16246
COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/16246 from sifmelcara:fix-platforms dbf3fd58dbfb3aca17831121c9e0681addc9aa21
PiperOrigin-RevId: 618198820
Co-authored-by: Ming-Chuan <10496191+sifmelcara@users.noreply.github.com>
|
|
(#16127) (#16264)
In https://github.com/protocolbuffers/protobuf/pull/15298 `"crosstool_top": "//external:android/crosstool"` was replaced with `"crosstool_top": "@platforms//os:android"`. This breaks users who have not migrated to https://bazel.build/concepts/platforms yet.
Closes #16127
COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/16127 from sifmelcara:add-back-legacy-crosstool-top c643235a3d4ff1fc0deaa9b440c288de1b099bcc
PiperOrigin-RevId: 615449874
Co-authored-by: Ming-Chuan <wtvwtvwtv2008@gmail.com>
|
|
Fix windows-only issue in our compiler unittests.
|
|
Fix windows-only issue in our compiler unittests.
|
|
The latest github runner image of ubuntu-22 includes a kernel update that breaks the sanitizers we use in our docker images. Long-term, we'll likely need to upgrade the images to new sanitizers and clang.
PiperOrigin-RevId: 616319042
|
|
Closes https://github.com/protocolbuffers/protobuf/issues/16026
PiperOrigin-RevId: 617333656
|
|
26.x 202403122011
|
|
|
|
|
|
26.x 202402282330
|
|
Add <shellapi.h> include for CommandLineToArgvW
|
|
This should fix the following error:
```
third_party\protobuf\src\google\protobuf\compiler\main.cc(127): error C3861: 'CommandLineToArgvW': identifier not found
```
PiperOrigin-RevId: 613319460
|
|
Resolve features directly in setProto instead of temporarily setting …
|
|
Avoid potential races with other threads reading features that do not share a lock while features are temporarily null.
Special handling for proto1 mutable should not actually be needed, since setProto doesn't update dependency protos.
PiperOrigin-RevId: 610783483
|
|
Actually fail if staleness fail
|
|
|
|
|
|
|
|
Updated amalgamations for PHP and Ruby.
|
|
PiperOrigin-RevId: 610833812
|
|
|
|
|
|
Remove rust proto libraries from the editions/BUILD file.
|
|
Ruby implement memsize functions for native types (#10291)
|
|
PiperOrigin-RevId: 605397582
|
|
Fix: https://github.com/protocolbuffers/protobuf/issues/10280
This allows Ruby to report a more correct estimation of the memory used by these objects.
It's useful when running memory profilers against applications.
cc @zhangskz @haberman
Closes #10291
COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/10291 from casperisfine:ruby-sizes 9150795328267e69a0b8e241dda675402e5633e2
PiperOrigin-RevId: 606718632
|
|
Cherry-pick fixes to install.cmake to escape regex special characters
|
|
Moved ObjectCache into an internal module.
|
|
CMake documentation (https://cmake.org/cmake/help/latest/command/string.html#regex-replace) indicates subexpressions are actually referenced via \1 not $1 in cmake.
PiperOrigin-RevId: 606307156
|
|
before REGEX REPLACE.
PiperOrigin-RevId: 605469982
|
|
We recently updated the codebase to comply with the Bazel layering check, which
essentially requires any C++ header inclusion to be matched with a build
dependency on a target providing that header.
As part of that, I removed a handful of dependencies from the `//:protobuf`
target, since these dependencies were not set up in a way that respected the
layering check. However, I realized that this may cause a number of breakages,
especially since we did not provide the correct public targets until very
recently.
This change effectively adds back in the missing dependencies, so that projects
which do not yet adhere to the layering check can continue to depend on them
indirectly. This way, we still adhere to the layering check and make it
possible for projects that depend on us to do so, but in most cases we won't
immediately break anyone.
PiperOrigin-RevId: 607021111
|
|
This type has always been internal-only, but moving it to a module named `Internal` will make this clearer.
PiperOrigin-RevId: 606649281
|
|
Until recently, these targets were dependencies of `//:protobuf` and could thus
be accessed through that target. But now that we are adhering to the layering
check, we need to provide proper access in a way that respects that check. This
change uses top-level alias targets following the existing pattern.
PiperOrigin-RevId: 605123979
|
|
26.x 202402061854
|