Skip to content

[AutoPR azure-resourcemanager-compute-bulkactions]-generated-from-SDK Generation - Java-6702286 - #49838

Closed
azure-sdk-automation[bot] wants to merge 5 commits into
mainfrom
sdkauto/azure-resourcemanager-compute-bulkactions-6569538
Closed

[AutoPR azure-resourcemanager-compute-bulkactions]-generated-from-SDK Generation - Java-6702286#49838
azure-sdk-automation[bot] wants to merge 5 commits into
mainfrom
sdkauto/azure-resourcemanager-compute-bulkactions-6569538

Conversation

@azure-sdk-automation

@azure-sdk-automation azure-sdk-automation Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Configurations: 'specification/compute/resource-manager/Microsoft.Compute/Bulkactions/tspconfig.yaml', and CommitSHA: 'e242531106b574c3f98fb7306dbceedd82b05f69' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6702286 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. Release plan link: https://azsdk-releaseplan-dashboard-hveph5aqhhcfhtgu.westus-01.azurewebsites.net/?releaseplan=35206 Submitted by:

Copilot AI review requested due to automatic review settings July 16, 2026 03:19
@azure-sdk-automation azure-sdk-automation Bot added the auto-release When merged to main, release pipelines for this PR's changed packages trigger automatically. label Jul 16, 2026

Copilot AI 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.

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

@github-actions github-actions Bot added the Mgmt This issue is related to a management-plane library. label Jul 16, 2026
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
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.

@weidongxu-microsoft

Copy link
Copy Markdown
Member

dup of #49664

@weidongxu-microsoft

Weidong Xu (weidongxu-microsoft) commented Jul 17, 2026

Copy link
Copy Markdown
Member

dup of #49664

Sorry, not a duplicate -- this is on a later preview api-version. But need to release the stable api-version first #49664

I will need to do a reset and regen here.

We still need a merge + resolve conflict after the release or above.

@weidongxu-microsoft
Weidong Xu (weidongxu-microsoft) force-pushed the sdkauto/azure-resourcemanager-compute-bulkactions-6569538 branch from a0cd80a to 0f5c6c2 Compare July 17, 2026 03:10
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
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.

…emanager-compute-bulkactions-6569538

# Conflicts:
#	sdk/compute/azure-resourcemanager-compute-bulkactions/CHANGELOG.md
@azure-sdk-automation azure-sdk-automation Bot changed the title [AutoPR azure-resourcemanager-compute-bulkactions]-generated-from-SDK Generation - Java-6569538 [AutoPR azure-resourcemanager-compute-bulkactions]-generated-from-SDK Generation - Java-6592964 Jul 21, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Regenerated against released 1.0.0-beta.1; CHANGELOG delta and diff verified, CI green.

@weidongxu-microsoft

Copy link
Copy Markdown
Member

This PR (compute-bulkactions 1.0.0-beta.2) is a duplicate of #49880, which targeted the same module and version with a larger generated surface and was merged to main on 2026-07-28. As a result, this branch now conflicts with main (90+ add/add conflicts across the whole module) because main already contains 1.0.0-beta.2 from #49880.

Since the duplicate has already shipped, resolving these conflicts here is not appropriate. Please close this PR (or regenerate on top of the current main if a further beta is intended).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 63ab2a0f-9d9f-4f4a-82a2-309f3fed6740
@azure-sdk-automation azure-sdk-automation Bot changed the title [AutoPR azure-resourcemanager-compute-bulkactions]-generated-from-SDK Generation - Java-6592964 [AutoPR azure-resourcemanager-compute-bulkactions]-generated-from-SDK Generation - Java-6702286 Aug 14, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Warning

Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.

What happened

The threat detection results could not be parsed.

Review the workflow run logs for details.

Automated management AutoPR review

  • Head SHA: 550f23a4dacd9ea55037f857fc84594deb22d6f8
  • Package: azure-resourcemanager-compute-bulkactions 1.0.0-beta.3
  • Release type: beta
  • API version: 2026-07-06-preview
  • CHANGELOG: 1.0.0-beta.3 (2026-08-14)
  • Java changes reviewed: non-generated management client and model changes in the synchronize range
  • Breaking changes: none (beta release)
  • Decision: no high-confidence concerns

Informational

  • MGMT-API-VERSION New — sdk/compute/azure-resourcemanager-compute-bulkactions/CHANGELOG.md release 1.0.0-beta.3 (2026-08-14) records generated API version 2026-07-06-preview; the package is correctly versioned as beta.

Automated management AutoPR review by Management AutoPR Review: https://github.com/Azure/azure-sdk-for-java/actions/runs/31771010069. Advisory only.

@weidongxu-microsoft

Copy link
Copy Markdown
Member

replaced by #50213

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-release When merged to main, release pipelines for this PR's changed packages trigger automatically. Mgmt This issue is related to a management-plane library.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants