Skip to content

build: bump client patch version to 2.112.2#27754

Open
dannimad wants to merge 1 commit into
release/client/2.112from
release-prep/2.112.0/6-patch-bump-2.112.2
Open

build: bump client patch version to 2.112.2#27754
dannimad wants to merge 1 commit into
release/client/2.112from
release-prep/2.112.0/6-patch-bump-2.112.2

Conversation

@dannimad

@dannimad dannimad commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Description

Bumps the client release group version on release/client/2.112 from 2.112.1 to 2.112.2.

@github-actions github-actions Bot added area: examples Changes that focus on our examples area: framework Framework is a tag for issues involving the developer framework. Eg Aqueduct area: tools area: runtime Runtime related issues area: loader Loader related issues area: driver Driver related issues area: dds Issues related to distributed data structures area: build Build related issues area: dev experience Improving the experience of devs building on top of fluid area: repo Repo related work area: website area: dds: sharedstring area: tests Tests to add, test infrastructure improvements, etc area: dds: propertydds area: odsp-driver area: dds: tree labels Jul 24, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Warning

WARNING: This PR is targeting a release branch!

All changes must first be merged into main and then backported to the target release branch.
Please include a link to the main PR in the description of this PR.

Changes to release branches require approval from the Patch Triage group before merging.
You should have already discussed this change with them so they know to expect it.

For more details, see our internal documentation for the patch policy and processes for
patch releases.

@github-actions github-actions Bot added the base: release PRs targeted against a release branch label Jul 24, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Hi! Thank you for opening this PR. Want me to review it?

Based on the diff (420 lines, 210 files), I've queued these reviewers:

  • Correctness — logic errors, race conditions, lifecycle issues
  • Security — vulnerabilities, secret exposure, injection
  • API Compatibility — breaking changes, release tags, type design
  • Performance — algorithmic regressions, memory leaks
  • Testing — coverage gaps, hollow tests

How this works

  • Adjust the reviewer set by ticking/unticking boxes above. Reviewer toggles alone don't trigger anything.

  • Tick Start review below to dispatch the review fleet.

  • After review finishes, tick Start review again to request another run — it auto-resets after each dispatch.

  • This comment updates as new commits land; your reviewer selections are preserved.

  • Start review

@jason-ha jason-ha left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good for when the time comes.
Note: we won't need to follow-up with prior version bump since there are no differences in packages from 2.112.0 to 2.112.1.

@dannimad
dannimad marked this pull request as ready for review July 24, 2026 18:22
@dannimad
dannimad requested a review from a team July 24, 2026 18:22
@github-actions

Copy link
Copy Markdown
Contributor

Bundle size comparison

Base commit: 1407bc85c2bc6c339504c58798090ef2873976f8
Head commit: 83638f28e011e3d1f41475b9621812cabae07e48

Pending — Build - client packages is running. Results will appear here when the build completes.

@dannimad
dannimad enabled auto-merge (squash) July 24, 2026 18:29
@jason-ha
jason-ha disabled auto-merge July 24, 2026 20:00
@jason-ha
jason-ha enabled auto-merge (squash) July 24, 2026 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: build Build related issues area: dds: propertydds area: dds: sharedstring area: dds: tree area: dds Issues related to distributed data structures area: dev experience Improving the experience of devs building on top of fluid area: driver Driver related issues area: examples Changes that focus on our examples area: framework Framework is a tag for issues involving the developer framework. Eg Aqueduct area: loader Loader related issues area: odsp-driver area: repo Repo related work area: runtime Runtime related issues area: tests Tests to add, test infrastructure improvements, etc area: tools area: website base: release PRs targeted against a release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants