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
In order to speed up version checking for the elixir segment, this change makes
it so that we first ask asdf for the elixir version, which is much faster.
If asdf is not installed or configured, the previous behavior of running
`elixir --version` will be used.
This also makes a minor fix to the elixir documentation, replacing 'flutter' with 'elixir'.
BREAKING CHANGE: you will need to migrate your current sitecore segment template
in case you have a custom one. Have a look at the documentation to see what changed.
Updated the Open Weather Map Current Weather URL to remove the
deprecated query parameter. Updated the URL to add the supported
latitude and longitude parameters.
Added a call to the Open Wetaher Map Geocoding API to resolve the
location parameter to latitude and longitude values as specified in the
Open Weather Map documentation.
Added properties to the Open Weather Map segment to allow users to
manually specify the latitude and longitude if desired. Doing this will
skip the geocoding API call and ignore the location parameter.
Updated the website documentation for the Open Weather Map segment to
reflect the property changes and explain how to use them.
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
BREAKING CHANGE: this property isn't used in any of the themes and it's
incorrect as fetching CPU information requires a timer which we don't
want to use as it will make rendering the prompt slower
For users who migrate to this version, remove the .CPU property from
the sysinfo segment's template in case you have that set.
resolves#3730
BREAKING CHANGE: this can cause existing manual hyperlinks
(`[text](link)`) to stop working. To fix, change those to
the following syntax: `«text»(link)`
resolves#3353
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
BREAKING CHANGE: this removes the posh-git segment. To mitigate,
rename the posh-git segment to git.
In case you had a custom template, make sure to migrate to the git
segment's template. You can now also leverage the same logic and
properties as the git segment in both the text template and/or
color templates.