@taskcluster/client 105.1.0 → 107.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@taskcluster/client",
-  "version": "105.1.0",
+  "version": "107.0.0",
   "author": "Jonas Finnemann Jensen <jopsen@gmail.com>",
   "description": "Client for interfacing taskcluster components",
   "license": "MPL-2.0",

package/src/apis.js

@@ -605,6 +605,33 @@ export default {
           "title": "Get Temporary GCP Credentials",
           "type": "function"
         },
+        {
+          "args": [
+            "appName",
+            "owner"
+          ],
+          "category": "Github Credentials",
+          "description": "Get a Github application installation token scoped to the given repositories\nand permissions, using the configured app `appName`.\n\nRequesting `<permission>: <level>` on `<owner>/<repo>` requires the scope\n`auth:github-repo-token:<appName>/<owner>/<repo>:<permission>:<level>`.\nLevels and permissions are matched exactly to github token permissions\nwhich can be found at\nhttps://docs.github.com/en/rest/apps/apps?apiVersion=2026-03-10#create-an-installation-access-token-for-an-app.\nWhile token access is widened (requesting a write token will give a read+write one)\nscopes are not. Holding `:contents:write` alone only allows requesting a `write` token.\nBoth owner and repo must be in lowercase in the scope.\n\nThe token expires after an hour but this behavior is github dependent.\nYou should read the `expires` property from the response if you intend\nto maintain active credentials in your task.",
+          "input": "v1/github-repo-token-request.json#",
+          "method": "post",
+          "name": "githubRepoToken",
+          "output": "v1/github-token-response.json#",
+          "query": [
+          ],
+          "route": "/github/<appName>/<owner>/repo-token",
+          "scopes": {
+            "AllOf": [
+              {
+                "each": "auth:github-repo-token:<appName>/<owner>/<repoPerm>",
+                "for": "repoPerm",
+                "in": "repoPerms"
+              }
+            ]
+          },
+          "stability": "experimental",
+          "title": "Get a repository scoped github token",
+          "type": "function"
+        },
         {
           "args": [
           ],
@@ -2982,32 +3009,6 @@ export default {
           "title": "Get an active provisioner",
           "type": "function"
         },
-        {
-          "args": [
-            "provisionerId"
-          ],
-          "category": "Worker Metadata",
-          "description": "Declare a provisioner, supplying some details about it.\n\n`declareProvisioner` allows updating one or more properties of a provisioner as long as the required scopes are\npossessed. For example, a request to update the `my-provisioner`\nprovisioner with a body `{description: 'This provisioner is great'}` would require you to have the scope\n`queue:declare-provisioner:my-provisioner#description`.\n\nThe term \"provisioner\" is taken broadly to mean anything with a provisionerId.\nThis does not necessarily mean there is an associated service performing any\nprovisioning activity.",
-          "input": "v1/update-provisioner-request.json#",
-          "method": "put",
-          "name": "declareProvisioner",
-          "output": "v1/provisioner-response.json#",
-          "query": [
-          ],
-          "route": "/provisioners/<provisionerId>",
-          "scopes": {
-            "AllOf": [
-              {
-                "each": "queue:declare-provisioner:<provisionerId>#<property>",
-                "for": "property",
-                "in": "properties"
-              }
-            ]
-          },
-          "stability": "deprecated",
-          "title": "Update a provisioner",
-          "type": "function"
-        },
         {
           "args": [
             "taskQueueId"
@@ -3122,33 +3123,6 @@ export default {
           "title": "Get a worker-type",
           "type": "function"
         },
-        {
-          "args": [
-            "provisionerId",
-            "workerType"
-          ],
-          "category": "Worker Metadata",
-          "description": "Declare a workerType, supplying some details about it.\n\n`declareWorkerType` allows updating one or more properties of a worker-type as long as the required scopes are\npossessed. For example, a request to update the `highmem` worker-type within the `my-provisioner`\nprovisioner with a body `{description: 'This worker type is great'}` would require you to have the scope\n`queue:declare-worker-type:my-provisioner/highmem#description`.",
-          "input": "v1/update-workertype-request.json#",
-          "method": "put",
-          "name": "declareWorkerType",
-          "output": "v1/workertype-response.json#",
-          "query": [
-          ],
-          "route": "/provisioners/<provisionerId>/worker-types/<workerType>",
-          "scopes": {
-            "AllOf": [
-              {
-                "each": "queue:declare-worker-type:<provisionerId>/<workerType>#<property>",
-                "for": "property",
-                "in": "properties"
-              }
-            ]
-          },
-          "stability": "deprecated",
-          "title": "Update a worker-type",
-          "type": "function"
-        },
         {
           "args": [
           ],