If you are manually building, and you have access to the \build folder, you can use this to get the next semver
Get-MFLatestSemverFromBuildManifest [[-ModulePath] <String>] [[-ConfigFile] <String>]
[[-ModuleNameOverride] <String>] [-ProgressAction <ActionPreference>] [<CommonParameters>]
Detailed Description
Get-MFLatestSemverFromBuildManifest
Import build\module\modulemanifest.psd1 Find the prerelease tag(if present) and module version. I.e. module version 1.1.0 prerelease tag prev003 = 1.1.0-prrev003
Major Minor Patch PreReleaseLabel BuildLabel —– —– —– ————— ———- 1 1 0 prev003
Root path of the module. Uses the current working directory by default
Type: String
Parameter Sets: (All)
Aliases: Path
Required: False
Position: 1
Default value: $(get-location).path
Accept pipeline input: True (ByPropertyName, ByValue)
Accept wildcard characters: False
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 2
Default value: ModuleForgeConfig.xml
Accept pipeline input: False
Accept wildcard characters: False
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 3
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
Type: ActionPreference
Parameter Sets: (All)
Aliases: proga
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.
Author: Adrian Andersson