Skip to content

Commit 617ff6e

Browse files
authoredNov 16, 2023
Upgrade Az version to 11.0.0 (#124)
* Support Az 11.0.0 * Polish changelog to highlight the major release alignment with Az.
1 parent a89f1c8 commit 617ff6e

File tree

93 files changed

+32235
-6075
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

93 files changed

+32235
-6075
lines changed
 

‎docs/how-to-update-az-module-spec.md

+8-5
Original file line numberDiff line numberDiff line change
@@ -48,14 +48,15 @@ Have the following installed on your system:
4848
$azModuleVersion = '5.6.0'
4949
5050
# execute
51-
.\powershell-module\Scripts\New-AzCmdletSpec.ps1 -AzVersion $azModuleVersion -OutputDirectory (Join-Path -Path (Get-Location) -ChildPath 'powershell-module\Az.Tools.Migration\Resources\ModuleSpecs\Az\'$azModuleVersion)
51+
.\powershell-module\Scripts\New-AzCmdletSpec.ps1 -AzVersion $azModuleVersion
5252
```
5353

5454
1. Remove the old module spec files from module resources:
55-
`powershell-module\Az.Tools.Migration\Resources\ModuleSpecs\Az\{old-version}`.
55+
`powershell-module\Az.Tools.Migration\Resources\ModuleSpecs\Az\Latest\{old-version}`.
5656

57-
1. Run the unit tests to make sure all unit tests pass. It's not uncommon for some tests to fail
58-
because the expected number of aliases or cmdlets from the specs has changed.
57+
1. Run the unit tests to make sure all unit tests pass.
58+
59+
It's common for some tests to fail because the expected number of aliases or cmdlets from the specs has changed. If so, please update the `$expectedAliasCount`/`$expectedCommandCount` in test files.
5960

6061
Restart PowerShell Process and navigate to the root folder of cloned Github repository
6162
```powershell
@@ -70,6 +71,8 @@ Have the following installed on your system:
7071

7172
Restart PowerShell if test is changed and module needs to be imported again.
7273

73-
1. Add new version and release notes to `powershell-module/ChangeLog.md` and `powershell-module/Az.Tools.Migration/Az.Tools.Migration.psd1`. It is usually patch release because no API changes
74+
1. Add new version and release notes to `powershell-module/ChangeLog.md` and `powershell-module/Az.Tools.Migration/Az.Tools.Migration.psd1`.
75+
76+
*Note: The major version of Az.Tools.Migration should be the major version of targeted Az Version. *
7477

7578
1. Submit a pull request to commit the new changes.

‎powershell-module/Az.Tools.Migration/Az.Tools.Migration.psd1

+3-2
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
RootModule = 'Az.Tools.Migration.psm1'
44

55
# Version number of this module.
6-
ModuleVersion = '2.0.1'
6+
ModuleVersion = '11.0.0'
77

88
# Supported PSEditions
99
CompatiblePSEditions = 'Core', 'Desktop'
@@ -108,7 +108,8 @@
108108
# IconUri = ''
109109

110110
# ReleaseNotes of this module
111-
ReleaseNotes = "* Fixed bug when using `Find-AzUpgradeCommandReference -DirectoryPath` #[121]"
111+
ReleaseNotes = "* Supported AzureRM to Az 11.0.0 migration. Now the major version of Az.Tools.Migration is aligned with the targeted Az version.
112+
* Fixed bug when using `Find-AzUpgradeCommandReference -DirectoryPath` #[121]"
112113
}
113114
}
114115

0 commit comments

Comments
 (0)
Please sign in to comment.