this is because we may have had a web.config file found (that is not for umbraco) before a *.csproj file is later found that does include umbraco installed
BREAKING CHANGE: exit segment is now called status segment.
The exit keyword is now deprecated and will be removed in a future
release. Please use the status keyword instead:
```diff
"segments": {
{
- "type": "exit"
+ "type": "status"
}
}
```
Additionally, the status segment configuration has changed to support
$PIPESTATUS. You can include a status template to customize the
rendering of each individual status code (supported in fish, zsh and
bash).
```json
"segments": {
{
"type": "status",
"properties": {
"status_template": "{{ if gt .Code 0 }}\uf071{{ else }}\uf00c{{ end }}",
"status_separator": " "
}
}
}
```
In case no $PIPESTATUS is available, the status segment will fall back
to the exit code of the last command using the status template
for rendering.
The `{{ .Meaning }}` property has been marked as deprecated and can be
replaced with `{{ reason .Code }}`, allowing it to be reused in
cross segment templates.
resolves#4070
BREAKING CHANGE: this deprecates support for Nerd Font V2 and
requires a compatible V3 Nerd Font. Note for users experiencing
issues with icons, update to the latest Nerd Font of your choice
this fixes an issue where using multiple powershell sessions with a
different Azure context would display the same context everywhere when
using Set-AzContext to switch between them
BREAKING CHANGE: this requires adding `$env:POSH_AZURE_ENABLED = $true`
to your PowerShell profile if you want to get the correct context
displayed in your prompt for Azure powershell
