[release]

This commit is contained in:
crschnick 2024-03-04 18:05:07 +00:00
parent 84378c18d8
commit d54fa908f8
2 changed files with 4 additions and 5 deletions

View file

@ -6,7 +6,7 @@ The versioning scheme has also been changed to simplify version numbers. So we a
The last few versions of XPipe from 1.7.16 to 8.0.1 all had a self-updater on Windows that was not working properly. This was caused by a newly introduced JDK bug. This is now fixed from 8.1 onwards. To upgrade to 8.1+ on Windows, you have to do it manually by downloading and installing it from https://github.com/xpipe-io/xpipe/releases. There shouldn't be any more problems with 8.1+ after that.
Not that versions <8.1 do not contain version information in the git vault. If you're on multiple systems that are synced with git, the git vault format can be updated on one system and being pulled on another a system that is running an older version. This can lead to data corruption. If this happens to you, you should be able to reset the git repository to a previous ref.
Note that versions <8.1 do not contain version information in the git vault. If you're on multiple systems that are synced with git, the git vault format can be updated on one system and being pulled on another a system that is running an older version. This can lead to data corruption. If this happens to you, you should be able to reset the git repository to a previous ref.
## New terminal launcher

View file

@ -4,17 +4,15 @@ The last few versions of XPipe from 1.7.16 to 8.0.1 all had a self-updater on Wi
To upgrade to 8.1+, you have to do it manually by downloading and installing it from https://github.com/xpipe-io/xpipe/releases. There shouldn't be any more problems with 8.1+ after that.
This also fixes opened terminal windows closing down when XPipe is closed on Windows. They will now stay open.
## Git Vault Versioning
When upgrading XPipe versions across many systems, one problem could have been the git vault format being updated on one system and being pulled on another a system that is running an older version. This could have led to data corruption. From now on, there will be a warning shown when the versions do not match up. From there you can choose to temporarily disable the git vault during a session until you upgrade to the matching version on that system as well.
If this happens to you, you should be able to reset the git repository to a previous ref.
This check however only works from 8.1 onwards. Older git vaults do not contain version information. So if this happens to you while updating from a previous version, e.g. 1.7.16, you should be able to reset the git repository to a previous ref.
## Filtering for hosts
You can now search for IPs and hostnames in addition to the connection names to filter your connection list. The connection a display when a filter is active has also been improved.
You can now search for IPs and hostnames in addition to the connection names to filter your connection list. The connection display when a filter is active has also been improved.
## File browser transfer fixes
@ -34,4 +32,5 @@ There is now a new action available in the file browser for directories on Windo
- Fix red validation markers appearing in front of other UI elements
- Fix msys2, cygwin, and gitforwindows shell environments being shown for the wrong parent connection when located on remote systems
- Fix transferred files with BOM sometimes getting corrupted on Windows systems
- Fix SSH askpass throwing errors on Windows systems where username contained special characters due to an OpenSSH bug
- Fix some null pointers