The Config Sync auto-upgrades feature is now unavailable. You can no longer configure auto-upgrade settings and must manually upgrade the Config Sync version

## Breaking The Config Sync auto-upgrades feature is now unavailable. You can no longer configure auto-upgrade settings and must [manually upgrade the Config Sync version](https://cloud.google.com/kubernetes-engine/enterprise/config-sync/docs/how-to/upgrade-config-sync#manually-upgrade). If you currently use auto-upgrades, you must first[disable auto-upgrades](https://cloud.google.com/kubernetes-engine/enterprise/config-sync/docs/how-to/upgrade-config-sync#disable-auto-upgrades)before you can manually update Config Sync. ## Breaking Upgraded the Open Telemetry Collector image from v0.103.0 to v0.118.0\. This upgrade includes a breaking change where the default OTLP component endpoint is now `localhost` instead of `0.0.0.0`. You will be impacted only if you use a customized configuration for the built-in Otel Collector within Config Sync, and you can explicitly specify `0.0.0.0` for endpoints to ensure that your monitoring solution continues to function correctly. To understand the changes in each release, review the full changelog for [opentelemetry-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CHANGELOG.md). ## Feature The `nomos vet` command now supports a `--threshold` flag to proactively validate the number of objects in your Config Sync repository. You can use this flag in validation pipelines to prevent sync failures caused by exceeding the underlying `etcd` size limits when your repository contains a large number of objects. For more information, see [Enforce the maximum number of objects to sync](https://cloud.google.com/kubernetes-engine/enterprise/config-sync/docs/how-to/nomos-command#threshold). ## Feature Deleting a RootSync or RepoSync now removes its management metadata from all managed objects. This allows objects to be adopted by their new managers, simplifying the procedure for splitting a large configuration repository across multiple RootSync or RepoSync objects. For more information, see [Break up a repository into multiple repositories](https://cloud.google.com/kubernetes-engine/enterprise/config-sync/docs/how-to/breaking-up-repo). ## Change Addressed multiple Common Vulnerabilities and Exposures (CVEs) by updating dependencies. ## Fix Fixed an issue impacting the [Ignore object mutations](https://cloud.google.com/kubernetes-engine/enterprise/config-sync/docs/concepts/configs#ignoring) feature. The `client.lifecycle.config.k8s.io/mutation: ignore` annotation was not always effective, causing Config Sync to potentially overwrite changes made directly to annotated resources in the cluster. Config Sync now correctly ignores mutations on these resources. ## Fix Fixed an issue preventing ResourceGroup objects from being garbage collected when their corresponding RootSync or RepoSync objects were deleted. ## Fix Fixed several issues to improve ResourceGroup status reporting and reliability. ## Fix Fixed an issue where drift prevention incorrectly blocked modifications of abandoned resources.