[ContentUnderstanding] Update release date for @azure/ai-content-understanding 1.1.0 - #38314
Merged
Merged
Conversation
chienyuanchang
requested review from
bojunehsu and
yungshinlintw
as code owners
April 28, 2026 00:03
chienyuanchang
enabled auto-merge (squash)
April 28, 2026 00:05
yungshinlintw
approved these changes
Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Packages impacted by this PR
@azure/ai-content-understanding
Issues associated with this PR
N/A
Describe the problem that is addressed by this PR
Updates the CHANGELOG.md release date for
@azure/ai-content-understanding1.1.0 to match the actual release date (2026-04-24).What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
N/A — metadata-only change.
Are there test cases added in this PR? (If not, why?)
No — changelog-only change, no functional impact.
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
N/A
Checklists