[Search 2026-04-01] java SDK codegen#49928
Draft
efrainretana with Copilot wants to merge 3 commits into
Draft
Conversation
|
Azure Pipelines: 35 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Co-authored-by: efrainretana <141282336+efrainretana@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Regenerate Azure Search SDK for API version 2026-04-01
[Search 2026-04-01] java SDK codegen
Jul 24, 2026
Co-authored-by: efrainretana <141282336+efrainretana@users.noreply.github.com>
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.
Regenerates
azure-search-documentsfrom spec commit18ebae7ea8f6aefd83268aacdb1f480b24842726(API2026-04-01, stable) and prepares the12.1.0release, based off and targetingrelease/azure-search-documents_12.1.0.Regenerating against the new spec commit yields byte-for-byte identical generated code to the released
12.0.0— the two commits differ only outside the Search2026-04-01data-plane surface.SearchCustomizations.javaapplies cleanly with no version/enum reconciliation needed (getLatest()already returns2026-04-01). This PR is therefore effectively a spec-pin refresh plus version metadata.Changes
tsp-location.yamlcommit →18ebae7ea8f6aefd83268aacdb1f480b24842726.12.0.0→12.1.0acrosspom.xml,README.md,src/samples/README.md, andeng/versioning/version_client.txt; dependentsdk/search/azure-search-perf/pom.xmlbumped to keep the{x-version-update;...;current}markers consistent (enforced bypom_file_version_scanner.ps1).## 12.1.0 (Unreleased)section noting the regeneration with no public API changes;12.0.0section preserved.Notes for reviewers
eng/versioning/version_client.txtandazure-search-perf/pom.xmlfall just outsideazure-search-documents/**but are the mandatory mechanical consequence of the version bump.