Skip to content

Commit 617c69e

Browse files
Merge pull request #188 from wei18/dependabot/submodules/Submodule/github/rest-api-description-1d62675
Bump Submodule/github/rest-api-description from `ad5a9d5` to `1d62675`
2 parents 87fe51e + 7bf82c8 commit 617c69e

8 files changed

Lines changed: 3279 additions & 374 deletions

File tree

Sources/actions/Types.swift

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9549,6 +9549,10 @@ public enum Components {
95499549
public var labels: [Components.Schemas.RunnerLabel]
95509550
/// - Remark: Generated from `#/components/schemas/runner/ephemeral`.
95519551
public var ephemeral: Swift.Bool?
9552+
/// The version of the GitHub Actions Runner software. This is only set if the runner has connected to the service at least once.
9553+
///
9554+
/// - Remark: Generated from `#/components/schemas/runner/version`.
9555+
public var version: Swift.String?
95529556
/// Creates a new `Runner`.
95539557
///
95549558
/// - Parameters:
@@ -9560,6 +9564,7 @@ public enum Components {
95609564
/// - busy:
95619565
/// - labels:
95629566
/// - ephemeral:
9567+
/// - version: The version of the GitHub Actions Runner software. This is only set if the runner has connected to the service at least once.
95639568
public init(
95649569
id: Swift.Int,
95659570
runnerGroupId: Swift.Int? = nil,
@@ -9568,7 +9573,8 @@ public enum Components {
95689573
status: Swift.String,
95699574
busy: Swift.Bool,
95709575
labels: [Components.Schemas.RunnerLabel],
9571-
ephemeral: Swift.Bool? = nil
9576+
ephemeral: Swift.Bool? = nil,
9577+
version: Swift.String? = nil
95729578
) {
95739579
self.id = id
95749580
self.runnerGroupId = runnerGroupId
@@ -9578,6 +9584,7 @@ public enum Components {
95789584
self.busy = busy
95799585
self.labels = labels
95809586
self.ephemeral = ephemeral
9587+
self.version = version
95819588
}
95829589
public enum CodingKeys: String, CodingKey {
95839590
case id
@@ -9588,6 +9595,7 @@ public enum Components {
95889595
case busy
95899596
case labels
95909597
case ephemeral
9598+
case version
95919599
}
95929600
}
95939601
/// Runner Application

Sources/apps/Client.swift

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1083,6 +1083,9 @@ public struct Client: APIProtocol {
10831083
///
10841084
/// Creates an installation access token that enables a GitHub App to make authenticated API requests for the app's installation on an organization or individual account. Installation tokens expire one hour from the time you create them. Using an expired token produces a status code of `401 - Unauthorized`, and requires creating a new installation token. By default the installation token has access to all repositories that the installation can access.
10851085
///
1086+
/// > [!NOTE]
1087+
/// > Starting April 27, 2026, GitHub began a staged rollout of a stateless format (`ghs_APPID_JWT`) to all newly minted GitHub App installation tokens, making them more performant and improving the reliability of our API surface. If your application expects or relies on installation tokens being exactly 40 characters long, it may not handle this new token format correctly. You can now validate your apps and workflows using a temporary request header that lets you enable the token format on demand. For more information about the temporary header, see [the GitHub blog](https://github.blog/changelog/2026-05-15-github-app-installation-tokens-per-request-override-header).
1088+
///
10861089
/// Optionally, you can use the `repositories` or `repository_ids` body parameters to specify individual repositories that the installation access token can access. If you don't use `repositories` or `repository_ids` to grant access to specific repositories, the installation access token will have access to all repositories that the installation was granted access to. The installation access token cannot be granted access to repositories that the installation was not granted access to. Up to 500 repositories can be listed in this manner.
10871090
///
10881091
/// Optionally, use the `permissions` body parameter to specify the permissions that the installation access token should have. If `permissions` is not specified, the installation access token will have all of the permissions that were granted to the app. The installation access token cannot be granted permissions that the app was not granted.

Sources/apps/Types.swift

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -110,6 +110,9 @@ public protocol APIProtocol: Sendable {
110110
///
111111
/// Creates an installation access token that enables a GitHub App to make authenticated API requests for the app's installation on an organization or individual account. Installation tokens expire one hour from the time you create them. Using an expired token produces a status code of `401 - Unauthorized`, and requires creating a new installation token. By default the installation token has access to all repositories that the installation can access.
112112
///
113+
/// > [!NOTE]
114+
/// > Starting April 27, 2026, GitHub began a staged rollout of a stateless format (`ghs_APPID_JWT`) to all newly minted GitHub App installation tokens, making them more performant and improving the reliability of our API surface. If your application expects or relies on installation tokens being exactly 40 characters long, it may not handle this new token format correctly. You can now validate your apps and workflows using a temporary request header that lets you enable the token format on demand. For more information about the temporary header, see [the GitHub blog](https://github.blog/changelog/2026-05-15-github-app-installation-tokens-per-request-override-header).
115+
///
113116
/// Optionally, you can use the `repositories` or `repository_ids` body parameters to specify individual repositories that the installation access token can access. If you don't use `repositories` or `repository_ids` to grant access to specific repositories, the installation access token will have access to all repositories that the installation was granted access to. The installation access token cannot be granted access to repositories that the installation was not granted access to. Up to 500 repositories can be listed in this manner.
114117
///
115118
/// Optionally, use the `permissions` body parameter to specify the permissions that the installation access token should have. If `permissions` is not specified, the installation access token will have all of the permissions that were granted to the app. The installation access token cannot be granted permissions that the app was not granted.
@@ -515,6 +518,9 @@ extension APIProtocol {
515518
///
516519
/// Creates an installation access token that enables a GitHub App to make authenticated API requests for the app's installation on an organization or individual account. Installation tokens expire one hour from the time you create them. Using an expired token produces a status code of `401 - Unauthorized`, and requires creating a new installation token. By default the installation token has access to all repositories that the installation can access.
517520
///
521+
/// > [!NOTE]
522+
/// > Starting April 27, 2026, GitHub began a staged rollout of a stateless format (`ghs_APPID_JWT`) to all newly minted GitHub App installation tokens, making them more performant and improving the reliability of our API surface. If your application expects or relies on installation tokens being exactly 40 characters long, it may not handle this new token format correctly. You can now validate your apps and workflows using a temporary request header that lets you enable the token format on demand. For more information about the temporary header, see [the GitHub blog](https://github.blog/changelog/2026-05-15-github-app-installation-tokens-per-request-override-header).
523+
///
518524
/// Optionally, you can use the `repositories` or `repository_ids` body parameters to specify individual repositories that the installation access token can access. If you don't use `repositories` or `repository_ids` to grant access to specific repositories, the installation access token will have access to all repositories that the installation was granted access to. The installation access token cannot be granted access to repositories that the installation was not granted access to. Up to 500 repositories can be listed in this manner.
519525
///
520526
/// Optionally, use the `permissions` body parameter to specify the permissions that the installation access token should have. If `permissions` is not specified, the installation access token will have all of the permissions that were granted to the app. The installation access token cannot be granted permissions that the app was not granted.
@@ -7123,6 +7129,9 @@ public enum Operations {
71237129
///
71247130
/// Creates an installation access token that enables a GitHub App to make authenticated API requests for the app's installation on an organization or individual account. Installation tokens expire one hour from the time you create them. Using an expired token produces a status code of `401 - Unauthorized`, and requires creating a new installation token. By default the installation token has access to all repositories that the installation can access.
71257131
///
7132+
/// > [!NOTE]
7133+
/// > Starting April 27, 2026, GitHub began a staged rollout of a stateless format (`ghs_APPID_JWT`) to all newly minted GitHub App installation tokens, making them more performant and improving the reliability of our API surface. If your application expects or relies on installation tokens being exactly 40 characters long, it may not handle this new token format correctly. You can now validate your apps and workflows using a temporary request header that lets you enable the token format on demand. For more information about the temporary header, see [the GitHub blog](https://github.blog/changelog/2026-05-15-github-app-installation-tokens-per-request-override-header).
7134+
///
71267135
/// Optionally, you can use the `repositories` or `repository_ids` body parameters to specify individual repositories that the installation access token can access. If you don't use `repositories` or `repository_ids` to grant access to specific repositories, the installation access token will have access to all repositories that the installation was granted access to. The installation access token cannot be granted access to repositories that the installation was not granted access to. Up to 500 repositories can be listed in this manner.
71277136
///
71287137
/// Optionally, use the `permissions` body parameter to specify the permissions that the installation access token should have. If `permissions` is not specified, the installation access token will have all of the permissions that were granted to the app. The installation access token cannot be granted permissions that the app was not granted.

0 commit comments

Comments
 (0)