Increment version

[alexathomases]

Description

This PR updates the HealthDataAIServices module to use our stable API version (2024-09-20).

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • [x] General release
  • [ ] Public preview
  • [ ] Private preview
  • [ ] Engineering build
  • [ ] No need for a release

• [x] Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately

  • For SDK-based development mode, update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • For autorest-based development mode, include the changelog in the PR description.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.

• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction

• SHOULD have proper test coverage for changes in pull request.

• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd[bot]]

️✔️Az.Accounts

>

>

️✔️Build

> >>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

⚠️Az.HealthDataAIServices

>

>

️✔️Build

> >>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

>

>

️✔️Breaking Change Check

> >>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

>

>

⚠️Signature Check

> >>

>>

⚠️PowerShell Core - Windows

>> >>|Type|Cmdlet|Description|Remediation| >>|---|---|---|---| >>|⚠️|Get-AzDeidService|Get-AzDeidService Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.|Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue| >>|⚠️|Get-AzDeidService|Get-AzDeidService changes the confirm impact. Please ensure that the change in ConfirmImpact is justified|Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.| >> >>

>

>

>

️✔️Help Example Check

> >>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

>

>

️✔️Help File Existence Check

> >>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

>

>

️✔️File Change Check

> >>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

>

>

️✔️UX Metadata Check

> >>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

>

>

️✔️Test

> >>

>>

️✔️PowerShell Core - Linux

>> >> >>

>>

>>

️✔️PowerShell Core - MacOS

>> >> >>

>>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

[alexathomases]

/azp run

[azure-pipelines[bot]]

Commenter does not have sufficient privileges for PR 26707 in repo Azure/azure-powershell

[VeryEarly]

/azp run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 3 pipeline(s).

[alexathomases]

/azp run

[azure-pipelines[bot]]

Commenter does not have sufficient privileges for PR 26707 in repo Azure/azure-powershell

[VeryEarly]

/azp run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 3 pipeline(s).

[alexathomases]

@VeryEarly I followed the guidance not to manually change the version in the README.md. How can I ensure that the version gets updated to 1.0.0 to indicate that this is a stable release, not preview?

[VeryEarly]

to become a stable version, we required preview version of module to be released for at least 2 months. This change will be published as 0.2.0 this time. Please ask for GA early next year.

Please also provide release notes in comment of this PR

[alexathomases]

to become a stable version, we required preview version of module to be released for at least 2 months. This change will be published as 0.2.0 this time. Please ask for GA early next year.

Please also provide release notes in comment of this PR

That makes sense - thank you. What is the process to ask for GA? Added description in PR comment.