When topgrade is run from within pwsh, the execution policy check breaks
for the Windows Update and Windows Store steps, because they use normal
powershell and the inherited PSModulePath environment variable breaks
the Microsoft.PowerShell.Security module import. So we unset that
variable to fix the issue, but also allow for those steps to use pwsh as
neither step actually requires PowerShell 5.
Co-authored-by: nistee <52573120+niStee@users.noreply.github.com>
* feat: initial i18n setup
* style: fmt
* feat: i18n support for new steps
* fix: build on Linux
* fix: build on Linux
* refactor: rm unused translation keys
---------
Co-authored-by: Steve Lau <stevelauc@outlook.com>
* Use global lazy HOME_DIR
* Remove unused base_dirs
* Use `etcetera` instead of `directories`
---------
Co-authored-by: Thomas Schönauer <37108907+DottoDev@users.noreply.github.com>
* Create `Sudo` type and `SudoKind` enum
* Fix build
* reformat
* Fix choco on windows
* Fix linux
* Fix linux more
* more fix stuff hehe hoho hahaha
* more fix stuff hehe hoho hahaha
Co-authored-by: Thomas Schönauer <37108907+DottoDev@users.noreply.github.com>
Fix `tmux` sessions
This will create a new session named `topgrade`, `topgrade-1`,
`topgrade-2`, using the first nonexistent session name it finds. That
session will have a window in it named `topgrade` in which `topgrade` is
run. If `topgrade --tmux` is being run from within tmux, it won't attach
to the new tmux session. If the user is not currently in tmux, it will
attach to the newly-created session.
Co-authored-by: Thomas Schönauer <37108907+DottoDev@users.noreply.github.com>
