beenull/xpipe-mirror
1
0
Fork 0
mirror of https://github.com/xpipe-io/xpipe.git synced 2024-11-25 09:00:26 +00:00
Code Issues Projects Releases Packages Wiki Activity

Update changelog

Browse source
This commit is contained in:
crschnick 2024-03-04 13:54:43 +00:00
parent 9a605a58e7
commit 492458c7f9
2 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
dist/changelogs/8.1.md vendored
View file

@ -4,9 +4,9 @@ The versioning scheme has also been changed to simplify version numbers. So we a
## Note on updating
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.
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.
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.
## New terminal launcher

3
dist/changelogs/8.1_incremental.md vendored
View file

@ -10,7 +10,7 @@ This also fixes opened terminal windows closing down when XPipe is closed on Win
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 problem already happened to you, you should be able to reset the git repository to a previous ref.
If this happens to you, you should be able to reset the git repository to a previous ref.
## Filtering for hosts
@ -34,4 +34,5 @@ There is now a new action available in the file browser for directories on Windo
- Better validate invalid settings values on startup
- Fix concurrency issues when querying multiple secrets at the same time
- 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 some null pointers