hydrusnetwork/hydrus v627-future-01

Version 627 Future 01

on GitHub

Advanced Users Only!

This is a test build of v627. It has:

• On All--
  • requests moved from 2.32.3 to 2.32.4 (security fix)
• On Linux and Windows--
  • PyInstaller moved from 6.7 to 6.14.1 (handles new numpy)
  • setuptools moved from 70.3.0 to 78.1.1 (security fix)
  • numpy moved from 2.2.6 to 2.3.1 (lots of improvements, py 3.11+)
• On Windows--
  • sqlite dll moved from 3.45.3 to 3.50.1

I do not know if this build will cause dll errors in a specific OS, so before I merge these updates into the normal release, I would like advanced users to simply try it out and see what happens.

So, if you would like to help me out:

• Extract it to your desktop or similar. DO NOT USE IN A REAL CLIENT IN YOUR FIRST ATTEMPT.
• Does it boot?
• If mpv works in your real client, does it still work here?
• How do your images look? Any incorrect colours or static?
• Do you have any UI issues, particularly stuff like menu positioning on a multi-monitor setup?

If it works with no problems and you are feeling brave, please test it on an existing installation so we can see if there are dll merge/overwrite conflicts:

• MAKE A BACKUP. IF YOU CANNOT BACKUP OR ARE UNCERTAIN HOW TO RESTORE, DO NOT DO THIS
• Warning: Do not use the test extract you made earlier on your desktop to update! This extract has a new database in it, and if you were to, say, drag and drop it on your real build, you would overwrite your real database. Update just as you normally would.
• Update exactly as you normally would using the downloaded build.
• Does it boot ok?
• If it does not boot ok, please do a clean install, as here: https://hydrusnetwork.github.io/hydrus/getting_started_installing.html#clean_installs
• If it still does not boot, rollback to your backup.

Let me know how you got on via email or discord or post on the release threads. I'd like to know your OS, too!

macOS users have a different situation, where an App will try to use your real release's db location by default, so the testing situation will have to be smarter, probably with a -d launch parameter. If you are a mac user and aren't sure what that means, do not try this!

Thanks!