Skip to content

Changes thats need to be included for 0.48.1 patch release#52

Open
vkarampudi wants to merge 11 commits intogoogle:r0.48.0from
vkarampudi:r0.48.0
Open

Changes thats need to be included for 0.48.1 patch release#52
vkarampudi wants to merge 11 commits intogoogle:r0.48.0from
vkarampudi:r0.48.0

Conversation

@vkarampudi
Copy link
Collaborator

No description provided.

tfx-copybara and others added 11 commits February 6, 2026 20:06
PiperOrigin-RevId: 743712449
* Add minimum viable mkdocs configuration

* Add examples section

* Add links to api docs and overviews

* Get api docs up and running

* Add `__all__` to `__init__.py` files to include correct classes

This is just a first step to including the correct items in the api docs

* Exclude test modules from docs

* Use correct module

* Add docs deployment workflow

* Include all correct modules/classes/functions

* Fix button rendering

* Fix formatting, including admonitions

* Fix broken link

* Use README.md as homepage for docs

* Fix links

* Remove debug triggers from docs deployment workflow

* Remove deprecated api docs

* Fix triggers

* Move docs requirements to common location

* Only trigger on pushes to master

* Remove unnecessary newline characters

* Move docs location to default `docs` directory
PiperOrigin-RevId: 796979132
PiperOrigin-RevId: 803375108
PiperOrigin-RevId: 809038483
PiperOrigin-RevId: 845226580
…y-pick into Release branch (google#49)

* Update WORKSPACE

* Update workspace.bzl

* Migrate to Protobuf 4.23.4: custom Bazel rule for Python proto generation

Protobuf 4.x removed py_proto_library and changed proto_library behavior. This commit:

- Creates _py_proto_library_rule: a custom Bazel rule that accepts ProtoInfo or PyInfo,
  runs protoc to generate Python _pb2.py files, and provides PyInfo for Python deps
- Replaces deprecated py_proto_library calls with custom rule implementation
- Configures protoc proto_path to include workspace dirs and external dependencies
- Adds local any.proto copies to bypass sandbox limitations in proto imports
- Applies compatibility patches to TensorFlow and TensorFlow Metadata dependencies
- Updates all s2t_proto_library_py calls to work with new implementation

Fixes: Protobuf 4.23.4 compatibility for struct2tensor build system

* Add compatibility patches for older Abseil and Protobuf 4.x

This patch extends tensorflow.patch with changes to support:

1. Abseil backward compatibility:
   - Add absl_base_prefetch.h compatibility shim for older Abseil
     versions that lack absl/base/prefetch.h
   - Update prefetch includes across TensorFlow/TSL to use the shim
   - Add inline implementation of NullTerminatedMessage for older
     Abseil versions without StatusMessageAsCStr

2. Protobuf 4.x support:
   - Refactor cc_proto_library to use native proto_library and
     cc_proto_library rules instead of custom proto_gen
   - Implement custom _tsl_py_proto_library_rule to replace the
     built-in py_proto_library removed in Protobuf 4.x
   - Update proto library generation to depend on generated
     cc_proto_library targets

3. Build cleanup:
   - Remove unused absl/strings:string_view dependency
   - Update BUILD files to reflect new dependency structure

These changes enable building struct2tensor with older Abseil versions
while supporting Protobuf 4.x, improving compatibility across different
dependency versions.

* chore: upgrade Protobuf dependency from 4.23.4 to 4.25.6

* Move TFMD patch to tfmd.patch; Protobuf 4.x compatibility

Remove vendored google/protobuf/any.proto and obsolete third_party/README.md

* fix: Use native prefix for Bazel rules in macros

Prefix cc_binary and cc_library with native. in struct2tensor.bzl

* Update Dockerfile

* Fix struct2tensor integration in TensorFlow Serving Docker build

Apply rules_cc patch before adding struct2tensor local repository to ensure proper Bazel configuration.

* Update RELEASE.md to sync with main branch

* Update version.py

---------

Co-authored-by: Gagandeep Singh <gdp.1807@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants