# 2025.30 Infrastructure Changes

## Changes on Application environment

| **Change** | **Name** | **Default** | **Example** | **Required** | **Applications** | **Short Description** |
|------------|----------|-------------|--------------|--------------|------------------|----------------------|
| New        | `SPEECH_SUPPORTED_LANGUAGES` | - | `en-US, it-IT, fr-FR, de-DE` | No | `speech` | Max 4 languages, they must be in Microsoft speech to text supported list. |
| New        | `SPEECH_SESSION_HARDCUT_TIMEOUT_MS` | - | `600000` (10min in millisecond) | No | `speech` | Hard cut for a speech session. Means it will automatically cutoff at the mark of 10min or whatever it was set to. |
| New        | `SPEECH_SESSION_NO_TRANSCRIPT_TIMEOUT_MS` | - | `30000` (30 seconds in milliseconds) | No | `speech` | If no transcript is received within 30 seconds (or whatever set) of each other, then we cutoff the connection. |
| New        | FEATURE_FLAG_ENABLE_SPACES_2_0_SHARE_MODAL_UN_11428 | - | true | No | `next-admin` | Enables new share feature on spaces 2.0 (only enable for clients using spaces 2.0) |

## Zitadel Upgrade to v2.71.13

### Overview

This release upgrades Zitadel to `v2.71.13`, to fix a security vulnerability. Link below to read more:

[https://github.com/zitadel/zitadel/security/advisories/GHSA-6c5p-6www-pcmr](https://github.com/zitadel/zitadel/security/advisories/GHSA-6c5p-6www-pcmr)

### Upgrade Instructions

1. **Preparation**
   - Take a backup of your current Zitadel instance if possible
   - Verify all external secrets are properly configured

2. **Configuration Update**
   Update the image tag in your Zitadel configuration:
   
   ```yaml
   image:
        tag: v2.71.13
   ```

3. **Deployment**
   - Apply the changes through your GitOps workflow (ArgoCD)
   - Monitor the deployment process
   - Verify all pods are green and running successfully

### Important Considerations

1. **Database**
   - No manual database migrations are required
   - Existing data will be preserved
   - Database schema remains compatible

2. **Authentication**
   - All existing authentication flows will continue to work
   - Session tokens remain valid
   - OIDC configurations are preserved

3. **Monitoring**
   - Monitor application logs for any issues
   - Check metrics for performance improvements
   - Verify all integrations are working as expected

### Rollback Plan

In case of migration issues:

1. Ensure the external secrets are properly configured
2. Revert the image tag to `v2.70.10`
3. Deploy this version again and ensure the pods are running successfully
4. Update the image tag to `v2.70.14`
5. Deploy this version and observe if migration was successful and pods are running successfully
6. Update to the desired image tag `v2.71.13`
7. Contact support if problems persist

### Support

For any issues during or after the upgrade:
- Check the Zitadel documentation
- Review application logs