@kapa.ai airbyte had any changes regarding temporal or temporal configurations in recent versions?

Yes, there have been some changes and discussions regarding Temporal in Airbyte. 1. There was an issue reported where the Temporal pod was crashing on Kubernetes for new deployments. This issue seems to have been resolved by updating to a newer Temporal version and using the upstream container image directly. If you don't give your db user database creation privileges then you need to set an environment variable to prevent Temporal from trying to create the db. Here is the code snippet for that:

yaml temporal:   extraEnv:     - name: SKIP_DB_CREATE       value: "true"

This was discussed in [Github Issue 25815](https://github.com/airbytehq/airbyte/issues/25815). 2. There was a discussion about adding externalTemporal as an option to the Helm chart. However, this issue was marked as stale due to inactivity and was closed later. You can find more details in [Github Issue 13212](https://github.com/airbytehq/airbyte/issues/13212). 3. There was also a discussion about setting Temporal Namespace, which is still an open issue. You can find more details in [Github Issue 18853](https://github.com/airbytehq/airbyte/issues/18853). 4. A security dependency bump for Temporal was also done as mentioned in [Github Issue 17075](https://github.com/airbytehq/airbyte/issues/17075). Please note that these changes and discussions are based on the provided knowledge sources and there might be more recent changes or discussions not covered in these sources.