build.ps1

# Line break for readability in AppVeyor console
Write-Host -Object ''

# Make sure we're using the Master branch and that it's not a pull request
# Environmental Variables Guide: https://www.appveyor.com/docs/environment-variables/
if ($env:APPVEYOR_REPO_BRANCH -ne 'master') {
	Write-Warning -Message "Skipping version increment and publish for branch $env:APPVEYOR_REPO_BRANCH"
} elseif ($env:APPVEYOR_PULL_REQUEST_NUMBER -gt 0) {
	Write-Warning -Message "Skipping version increment and publish for pull request #$env:APPVEYOR_PULL_REQUEST_NUMBER"
} else {
	# We're going to add 1 to the revision value since a new commit has been merged to Master
	# This means that the major / minor / build values will be consistent across GitHub and the Gallery
	Try {
		# This is where the module manifest lives
		$manifestPath = '.\IAUtility\IAUtility.psd1'

		# Start by importing the manifest to determine the version, then add 1 to the revision
		$manifest = Test-ModuleManifest -Path $manifestPath
		[System.Version]$version = $manifest.Version
		Write-Output "Old Version: $version"
		[String]$newVersion = New-Object -TypeName System.Version -ArgumentList ($version.Major, $version.Minor, $version.Build, ($version.Revision + 1))
		Write-Output "New Version: $newVersion"

		# Update the manifest with the new version value and fix the weird string replace bug
		$functionList = ((Get-ChildItem -Path .\IAUtility\Public).BaseName)
		Update-ModuleManifest -Path $manifestPath -ModuleVersion $newVersion -FunctionsToExport $functionList
		(Get-Content -Path $manifestPath) -replace 'PSGet_IAUtility', 'IAUtility' | Set-Content -Path $manifestPath
		(Get-Content -Path $manifestPath) -replace 'NewManifest', 'IAUtility' | Set-Content -Path $manifestPath
		(Get-Content -Path $manifestPath) -replace 'FunctionsToExport = ', 'FunctionsToExport = @(' | Set-Content -Path $manifestPath -Force
		(Get-Content -Path $manifestPath) -replace "$($functionList[-1])'", "$($functionList[-1])')" | Set-Content -Path $manifestPath -Force
	} catch {
		throw $_
	}

	# Update the docs
	Write-Host "Building new documentation" -ForegroundColor Yellow
	. .\docs\Update-Documentation.ps1
	Write-Host -Object ''

	# Publish the new version to the PowerShell Gallery
	Try {
		# Build a splat containing the required details and make sure to Stop for errors which will trigger the catch
		$PM = @{
			Path        = '.\IAUtility\'
			NuGetApiKey = $env:NuGetApiKey
			ErrorAction = 'Stop'
		}
		Publish-Module @PM
		Write-Host "IAUtility PowerShell Module version $newVersion published to the PowerShell Gallery." -ForegroundColor Cyan
	} Catch {
		# Sad panda; it broke
		Write-Warning "Publishing update $newVersion to the PowerShell Gallery failed."
		throw $_
	}

	# Publish the new version back to Master on GitHub
	Try {
		# Set up a path to the git.exe cmd, import posh-git to give us control over git, and then push changes to GitHub
		# Note that "update version" is included in the appveyor.yml file's "skip a build" regex to avoid a loop
		$env:Path += ";$env:ProgramFiles\Git\cmd"
		Import-Module posh-git -ErrorAction Stop
		git checkout master
		git add --all
		git status
		git commit -s -m "Update version to $newVersion"
		git push origin master
		Write-Host "IAUtility PowerShell Module version $newVersion published to GitHub." -ForegroundColor Cyan
	} Catch {
		# Sad panda; it broke
		Write-Warning "Publishing update $newVersion to GitHub failed."
		throw $_
	}
}