Request for Detailed Upgrade Procedure

Support
1

I have…

  • Read the following guideline: Troubleshooting and Support | Squidex. I understand that my support request might get deleted if I do not follow the guideline.
  • Used code blocks with ``` to format my code examples like JSON or logs properly.

I’m submitting a…

  • Regression (a behavior that stopped working in a new release)
  • Bug report
  • Performance issue
  • Documentation issue or request

Current behavior

a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; }

Request for Detailed Upgrade Procedure (7.6.1‑oauth2 → 7.15.0 / latest)

Hi everyone,

we are currently running different Squidex versions across our environments and would like to align them to a newer stable release.
Here are our current versions:

Dev:   squidex:7.15.0
Stage: squidex-stage:7.6.1-oauth2
Prod:  squidex-stage:7.6.1-oauth2

Before proceeding, I would like to ask for clear and detailed guidance about the recommended upgrade process.
Specifically:

Questions

  1. What is the correct upgrade path from 7.6.1-oauth2 to 7.15.0 or the current stable version?
  • Is a direct upgrade supported, or should we upgrade through intermediate versions?
  1. Are there any breaking changes or compatibility issues we should be aware of between these versions?
  2. Does this upgrade require database migrations, long‑running operations, or additional downtime planning?
  3. Are there configuration changes needed, especially related to OAuth2 (given the -oauth2 image tag)?
  4. What are the best practices for upgrading production environments with minimal impact?

Thanks in advance for your help!
If there is official documentation or guides covering this scenario, please feel free to share them.