Get the highest build number and use that value for latest.txt

[catilac]

Fixes #719

I used Claude to take the Issue and make a fix, and then hand checked the actual code. For now this will just take the highest build number.

The more robust fixes I think can come later, because I want to take a second to think through our system as we start to put out 5.0 beta releases, too.

Thanks for pointing this out and suggesting a fix!

Note: After merging, we'll need to re-run the build action

[netlify]

✅ Deploy Preview for java-processing-faf822 ready!

Name	Link
🔨 Latest commit	c2dde33
🔍 Latest deploy log	https://app.netlify.com/projects/java-processing-faf822/deploys/6ac3d89e46ad180008a0d88a
😎 Deploy Preview	https://deploy-preview-722--java-processing-faf822.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[SableRaf]

The more robust fixes I think can come later, because I want to take a second to think through our system as we start to put out 5.0 beta releases, too.

Yes that makes sense. I was wondering about that too. Processing 4 users should probably not get prompted for updates when a Processing 5.x version is released, at least as long as new versions of Processing 4 continue to be released in parallel.

Either way, seems like a reasonable fix for now.

[SableRaf]

Looks good to me. I didn't stare to closely at the logic, but the latest.txt in the deploy preview correctly shows 1435 as the revision number.

https://deploy-preview-722--java-processing-faf822.netlify.app/download/latest.txt