v0.9.0

[dkorecko]

Hello, quite a big update coming up once again!

Let's get right to it:

Settings tab

With the new updates there was a need for a settings page, so I have added one. It can be found in the navigation menu and allows the configuration of the features mentioned down below.

LLM-based security scanning

It didn't feel right allowing automatic updates without adding any checks that would be too time-consuming for a single person to do on a regular basis for each application. Here come LLM-based security scanning.

If you have configured ollama via the environment variables (check the README for instructions), you can go into the Settings and enable security scanning. For each detected update for an application, this will feed all the changes between the two releases to the codebase into your ollama instance, which will provide a security analysis and also determine if there are any new threats. This also supports chunking for when the diff is too large to fit into your provided context (also check README for how to provide context size). This is included in the update notification and the versions page.

Automatic updates

Finally I felt confident enough to include the feature for enabling automatic updates. Meaning, if you enable automatic updates and set a specific threshold, when an update for any app comes up, it will wait for that specific period of time and then execute the update automatically. For an app to be eligible for an automatic update, these conditions will need to be met:

• Able to generate an update plan
• There are no breaking changes (either algorithm-based or AI-detected)
• There are no security threats detected

In case an automatic update fails, it's handled just the same way as any other update. It will show up in update attempts and you will receive a notification about it to your configured notifications channels.

Quality of life updates

The version is now displayed in the UI and the About link was replaced with a GitHub link.

Now you can open multiple accordions, not just one.

Hope you enjoy the new release and let me know if there are any issues!

What's Changed

• feat: Automatic updates by @dkorecko in feat: Automatic updates #77
• feat: Security analysis by @dkorecko in feat: Security analysis #78
• feat: Send notification when automatic update concludes by @dkorecko in feat: Send notification when automatic update concludes #80
• feat: Display application version in UI, pass release version to Docker labels and don't collapse when opening different accordion by @dkorecko in feat: Display application version in UI, pass release version to Docker labels and don't collapse when opening different accordion #81

Full Changelog: v0.8.0...v0.9.0

---

This discussion was created from the release v0.9.0.

[robant85]

Can someone help me understand how I may be misusing the service? Most of my Portainer compose have the ":latest" tag, and PatchPanda is telling me that several of my containers are a version behind. I think I have surmised that if I'm not pointing to a specific GitHub release in my compose, that PatchPanda doesn't actually know which version I am on? Even with the Portainer integration?

I essentially want to use PatchPanda how it's designed to update my stack ONLY if there are non-breaking changes. Why is it telling me that my version is outdated, when checking the application itself shows that it's updated fully?

What do I have setup incorrectly?

[dkorecko]

Hey, well most importantly, PatchPanda doesn't support latest tags at all as it goes against how it's supposed to function, so I'd recommend pinning versions (since it will handle the updates anyway) and then most likely everything will be detected properly. Obviously if not you can open an issue for the specific cases.

[robant85]

Kinda what I figured. Your app is awesome, so I guess I gotta change my ways to use it. Thank you.

[dkorecko]

Thanks for the kind words! If you have thoughts on how we could make it work with latest tags you can share them in #33 (and also to see why I don't think it's a good approach) though.