You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure Pipelines:
Successfully started running 1 pipeline(s).
9 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.
The recordings were made at 2026-06-01, so playback failed after the 2026-09-01
regeneration. Re-record all hand-written tests live against the canary endpoint
(eastus2euap) and update the assets tag. Point the live-only CRUD test at the same
canary defaults as the other tests, since 2026-09-01 is only in the canary manifest.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
The API-version documentation incorrectly advertises support for None, which causes get_limits() to fail, and the changelog omits the Python minimum-version increase from 3.9 to 3.10.
Updates generated clients, request types, examples, and release metadata; raises the minimum Python version to 3.10.
Moves CRUD test defaults to the canary environment and updates recorded assets.
Paths below are relative to sdk/fileshares/azure-mgmt-fileshares/. Generated samples and tests are listed for completeness but excluded from detailed review under repository guidance.
File
Description
tsp-location.yaml
Pins the updated TypeSpec source commit.
tests/test_fileshares_crud.py
Uses canary endpoint and resource defaults.
README.md
Updates authentication terminology to Microsoft Entra.
pyproject.toml
Marks the package stable and requires Python 3.10+.
…lists
The tests created shares in a resource group shared with other test suites, and listing by
subscription returns every share in the shared test subscription, so recordings captured
unrelated resources' names, IDs and host names.
- Default FILESHARES_TEST_RG to azsdk-python-fileshares-rg, used only by these tests.
- conftest.py: while recording, keep only that resource group's shares in recorded file
share list responses.
- Re-recorded all tests against the canary endpoint and updated the assets tag.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
Client documentation incorrectly advertises support for api_version=None, which causes operations to fail, and release notes omit the new Python 3.10+ requirement.
This release raises requires-python from 3.9 to 3.10, but the new 1.0.0 changelog only lists added features. Please add an entry explicitly stating that Python 3.9 is no longer supported so users can identify the compatibility change before upgrading.
Document the async client's actual API version default
The async client also advertises api_version=None, but its configuration preserves that value and operation validation rejects it; for example, start_redundancy_conversion raises a ValueError before sending a request. Please regenerate the documentation with the actual 2026-09-01 default and remove None from the supported values unless the fallback is implemented.
API version 2026-09-01 is not yet available in the public ARM manifest, so release this as a
beta instead of the first stable release: version 1.0.0b2, 'Development Status :: 4 - Beta'
and is_stable = false. A stable 1.0.0 follows once 2026-09-01 is publicly available.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
The API metadata incorrectly labels prerelease 1.0.0b2 as stable 1.0.0, while documentation omits dropped Python 3.9 support and advertises an unsupported None API version.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The generated client documentation incorrectly advertises api_version=None as supported, although explicitly passing it causes operations such as get_limits to raise ValueError instead of using the default.
Azure Pipeline build 7024664 (job: python - pullrequest, task: "Create APIView if API has changes") failed in the Detect-Api-Changes.ps1 PowerShell step with:
PowerShell exited with code '1'.
The term 'System.PullRequest.PullRequestNumber' is not recognized as a name of a cmdlet, function, script file, or executable program.
Relevant pipeline output
[command]/usr/bin/pwsh -NoLogo -NoProfile -NonInteractive -Command . '/mnt/vss/_work/_temp/cd625aa5-6c4f-4a42-a86c-b82ecd0aae07.ps1'
System.PullRequest.PullRequestNumber: /mnt/vss/_work/_temp/cd625aa5-6c4f-4a42-a86c-b82ecd0aae07.ps1:3
Line |
3 | ... 664 -PullRequestNumber $(System.PullRequest.PullRequestNumber) -RepoF ...
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| The term 'System.PullRequest.PullRequestNumber' is not recognized as a
| name of a cmdlet, function, script file, or executable program. Check
| the spelling of the name, or if a path was included, verify that the
| path is correct and try again.
##[error]PowerShell exited with code '1'.
Root cause
The step is defined in the shared pipeline template eng/common/pipelines/templates/steps/detect-api-changes.yml (line 22), which invokes Detect-Api-Changes.ps1 with -PullRequestNumber $(System.PullRequest.PullRequestNumber). Azure Pipelines did not substitute the $(System.PullRequest.PullRequestNumber) variable macro before the PowerShell script ran — it was passed through literally. PowerShell then tried to interpret the raw, unquoted token System.PullRequest.PullRequestNumber as a positional/command argument, producing "not recognized as a name of a cmdlet" and failing the step.
This indicates the System.PullRequest.PullRequestNumber predefined variable was not available/populated in this build's context, rather than an issue with any file changed in this PR. None of the 62 files modified in this PR touch eng/common/pipelines/ or the Detect-Api-Changes.ps1 script — the failure is in a shared engineering pipeline template unrelated to the azure-mgmt-fileshares SDK generation changes in this PR.
Recommended next steps
Re-run/retry the python - pullrequest pipeline — this is often transient when the System.PullRequest.* variable group isn't populated for a particular trigger/run.
If it recurs across multiple PRs, file an issue against eng/common/pipelines/templates/steps/detect-api-changes.yml to add a guard (e.g., quote the variable or skip the step when System.PullRequest.PullRequestNumber is empty) so a missing variable doesn't crash the step.
Copilot detected the failing pipeline and generated the analysis above. To have it attempt a fix automatically, reply with @copilot please fix the failing pipeline on this PR.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
Service-owner confirmation is needed before the stable 1.0.0 release because the changed CRUD-test comment identifies API 2026-09-01 as canary-only, and the supplied evidence does not establish production ARM availability.
Azure Pipelines:
Successfully started running 1 pipeline(s).
This branch has not been deployed
No deployments
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
auto-releaseWhen merged to main, release pipelines for this PR's changed packages trigger automatically.
3 participants
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.
SDK generation details
Note
This pull request was generated automatically.
specification/fileshares/resource-manager/Microsoft.FileShares/FileShares/tspconfig.yamlatcec8aacjlindamood@microsoft.comImportant
Complete the SDK release prerequisites before release.