Upgrade path from v2.5.7 to v2.5.41 incremental or direct jump?

[Gmanweb]

Hi everyone,

We're running MISP on Kubernetes (Helm-deployed) and looking to upgrade. I'd appreciate guidance on the upgrade path.
Current setup:

• MISP Core: v2.5.7 (image: ghcr.io/misp/misp-docker/misp-core:v2.5.7)
• MISP Modules: v2.4.201 (image: ghcr.io/misp/misp-docker/misp-modules:v2.4.201)
• Redis: 7.2.12 (Bitnami)
• Database: AWS Aurora PostgreSQL (external, not bundled)
• Helm: Custom chart (v0.1.0)

Target: v2.5.41

Questions:

1. Can I jump directly from v2.5.7 → v2.5.41? Or do I need to upgrade incrementally through specific intermediate versions? (I see ~34 releases between these versions with multiple DB schema changes)
2. Are there breaking changes in this range that require manual intervention beyond just changing the image tag and letting the container run its DB migrations on startup?
3. Redis → Valkey: The official helm chart (v1.0.0) now uses Valkey instead of Redis. Is Valkey required for v2.5.41, or will Redis 7.x continue to work?
4. MISP Modules compatibility: What modules image tag is compatible with core v2.5.41? We're currently on v2.4.201.
5. Database migrations: Do the schema migrations run automatically on container startup, or do I need to run them manually via CLI for a jump this large?

Any help is appreciated happy to share more detail about our setup if needed.

[Gmanweb]

If you're interested in this topic, I've filed an issue in the misp-docker repository to gain better visibility and solicit community help: MISP/misp-docker#429

[iglocska]

1. No need for incremental changes. The first request will incrementally update the db.
2. Nope, that should be it.
3. Redis will continue to work, we made the change because redis stopped being open source for a while.
4. they all should be backwards compatible, nothing has changed in the protocol itself. Though I would update misp modules too.
5. This is best asked in the docker room, but afaik the startup includes the runupdates command. If not, on first login it will automatically run it anyway though.