taskcluster 110.0.0__tar.gz → 110.1.0__tar.gz

{taskcluster-110.0.0 → taskcluster-110.1.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: taskcluster
-Version: 110.0.0
+Version: 110.1.0
 Summary: Python client for Taskcluster
 Project-URL: Homepage, https://github.com/taskcluster/taskcluster
 Project-URL: Repository, https://github.com/taskcluster/taskcluster

{taskcluster-110.0.0 → taskcluster-110.1.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "taskcluster"
-version = "110.0.0"
+version = "110.1.0"
 description = "Python client for Taskcluster"
 readme = "README.md"
 license = {text = "MPL-2.0"}

{taskcluster-110.0.0 → taskcluster-110.1.0}/taskcluster/generated/aio/workermanager.py

@@ -269,6 +269,10 @@ class WorkerManager(AsyncBaseClient):
         Create a new worker.  This is only useful for worker pools where the provider
         does not create workers automatically, such as those with a `static` provider
         type.  Providers that do not support creating workers will return a 400 error.
+        Worker IDs cannot be reused after removal.
+        If the ID belongs to a stopped worker or conflicts with an existing worker,
+        this method returns a 409 error.
+        Use `updateWorker` to modify an existing worker instead.
         See the documentation for the individual providers, and in particular the
         [static provider](https://docs.taskcluster.net/docs/reference/core/worker-manager/)
         for more information.

{taskcluster-110.0.0 → taskcluster-110.1.0}/taskcluster/generated/workermanager.py

@@ -251,6 +251,10 @@ class WorkerManager(BaseClient):
         Create a new worker.  This is only useful for worker pools where the provider
         does not create workers automatically, such as those with a `static` provider
         type.  Providers that do not support creating workers will return a 400 error.
+        Worker IDs cannot be reused after removal.
+        If the ID belongs to a stopped worker or conflicts with an existing worker,
+        this method returns a 409 error.
+        Use `updateWorker` to modify an existing worker instead.
         See the documentation for the individual providers, and in particular the
         [static provider](https://docs.taskcluster.net/docs/reference/core/worker-manager/)
         for more information.

{taskcluster-110.0.0 → taskcluster-110.1.0}/taskcluster/helper.py

@@ -10,8 +10,8 @@ from datetime import timezone
 
 import requests
 
-from taskcluster.generated import _client_importer
-from taskcluster.generated.aio import _client_importer as _async_client_importer
+import taskcluster
+import taskcluster.aio
 from taskcluster.utils import stringDate
 
 logger = logging.getLogger(__name__)
@@ -77,8 +77,8 @@ class TaskclusterConfig:
         if self.options is None:
             self.auth()
 
-        client_importer = _async_client_importer if use_async else _client_importer
-        service = getattr(client_importer, service_name.capitalize(), None)
+        clients = taskcluster.aio if use_async else taskcluster
+        service = getattr(clients, service_name.capitalize(), None)
         assert service is not None, f"Invalid Taskcluster service {service_name}"
         return service(self.options)
 

{taskcluster-110.0.0 → taskcluster-110.1.0}/uv.lock

@@ -1334,7 +1334,7 @@ wheels = [
 
 [[package]]
 name = "taskcluster"
-version = "110.0.0"
+version = "110.1.0"
 source = { editable = "." }
 dependencies = [
     { name = "aiohttp" },