Browse Source

chore: remove outdated info from stability doc (#5971)

Signed-off-by: Gergely Brautigam <182850+Skarlso@users.noreply.github.com>

On-behalf-of: Gergely Brautigam <gergely.brautigam@sap.com>
Gergely Bräutigam 3 months ago
parent
commit
68e0bf38a7
1 changed files with 0 additions and 10 deletions
  1. 0 10
      docs/introduction/stability-support.md

+ 0 - 10
docs/introduction/stability-support.md

@@ -44,22 +44,12 @@ As of version 0.14.x , this is the only kubernetes version that we will guarante
 
 ## Upgrading
 
-External Secrets Operator has not reached stable 1.0 yet. This means that **we treat each minor version bump as a potentially breaking change**. Breaking changes may include:
-
-- API schema changes
-- Default behavior modifications
-- Deprecated feature removals
-- Provider authentication changes
-- Configuration format updates
-
 **Important upgrade recommendations:**
 
 1. **Plan your upgrades carefully** - Always review release notes before upgrading, it could contain breaking changes information
 2. **Upgrade version by version** - We strongly recommend upgrading one minor version at a time (e.g., 0.18.x → 0.19.x → 0.20.x) rather than skipping versions
 3. **Test in non-production first** - Always validate upgrades in development/staging environments
 
-Until we reach v1.0, please treat minor version upgrades with the same caution you would give to major version upgrades in other projects.
-
 ## Provider Stability and Support Level
 
 The following table describes the stability level of each provider and who's responsible.