diff --git a/content/actions/concepts/security/openid-connect.md b/content/actions/concepts/security/openid-connect.md index 8a0f0b41df90..140a46861367 100644 --- a/content/actions/concepts/security/openid-connect.md +++ b/content/actions/concepts/security/openid-connect.md @@ -88,6 +88,9 @@ The following example OIDC token uses a subject (`sub`) that references a job en } ``` +> [!NOTE] +> The `sub` claim in this example uses the previous format. Repositories created after July 15, 2026 use an immutable default subject format that includes owner and repository IDs (not available on {% data variables.product.prodname_ghe_server %}). For more information, see [AUTOTITLE](/actions/reference/security/oidc#immutable-subject-claims). + {% ifversion ghec %} ## Establishing OIDC trust with your cloud provider diff --git a/content/code-security/concepts/supply-chain-security/automatic-dependabot-access-to-github-registries.md b/content/code-security/concepts/supply-chain-security/automatic-dependabot-access-to-github-registries.md deleted file mode 100644 index 8661d3c173f2..000000000000 --- a/content/code-security/concepts/supply-chain-security/automatic-dependabot-access-to-github-registries.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Automatic Dependabot access to {% data variables.product.github %}-hosted registries -intro: 'Keep your private dependencies up to date reliably by granting {% data variables.product.prodname_dependabot %} automatic access to {% data variables.product.prodname_registry %} and {% data variables.product.prodname_container_registry %}, so you never need to create or rotate credentials for these registries.' -versions: - feature: org-automatic-registry-access -shortTitle: Automatic registry access -allowTitleToDifferFromFilename: true -contentType: concepts -category: - - Secure your dependencies ---- - -## About automatic access to {% data variables.product.github %}-hosted registries - -{% data variables.product.prodname_dependabot %} can authenticate to private {% data variables.product.prodname_registry %} and {% data variables.product.prodname_container_registry %} packages using the same access grants that {% data variables.product.prodname_actions %} workflows use. If a package has granted your repository **Read** access in the package settings on {% data variables.product.github %}, {% data variables.product.prodname_dependabot %} can access that package automatically. - -This eliminates the need to: - -* Create and manage {% data variables.product.pat_generic_plural %} for registry access -* Manually configure access to {% data variables.product.github %}-hosted registries in your `dependabot.yml` file -* Rotate credentials when tokens expire - -## How automatic access works - -{% data variables.product.prodname_dependabot %} uses its `GITHUB_TOKEN` to request `packages: read` permission when pulling from `*.pkg.github.com` and {% data variables.product.prodname_container_registry_namespace %}. Any package that has granted your repository access through "Manage Actions access" accepts this token, the same way it would for a regular {% data variables.product.prodname_actions %} workflow. See [AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package).git s - -This works for every {% data variables.product.prodname_registry %} ecosystem that {% data variables.product.prodname_dependabot %} supports. - -## When to use automatic access - -Use automatic access to {% data variables.product.github %}-hosted registries when: - -* Your repositories depend on private packages stored in {% data variables.product.prodname_registry %} or {% data variables.product.prodname_container_registry %}. -* You want to reduce credential management overhead. -* You want to avoid silent update failures caused by expired {% data variables.product.pat_generic_plural %}. - -For third-party registries (such as Artifactory, Azure Artifacts, or Nexus), you can only use the `dependabot.yml` registry configuration or organization-level private registry settings. See [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-access-to-private-registries). - -## How to enable automatic access - -For each package that {% data variables.product.prodname_dependabot %} needs to read, you need to go to the package's settings page and add the repository that runs {% data variables.product.prodname_dependabot %} with **Read** access. See [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-access-to-private-registries#configuring-private-github-hosted-registries). - -Once the repository has been granted access, {% data variables.product.prodname_dependabot %} can pull from that package automatically. You do not need to configure the `dependabot.yml` file, and you can remove any existing {% data variables.product.pat_generic %}-based registry entries you previously added for these packages. - -For more information about configuring package access, see [AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package). diff --git a/content/code-security/concepts/supply-chain-security/index.md b/content/code-security/concepts/supply-chain-security/index.md index 56a840696725..4ba0f860b15e 100644 --- a/content/code-security/concepts/supply-chain-security/index.md +++ b/content/code-security/concepts/supply-chain-security/index.md @@ -8,6 +8,7 @@ versions: contentType: concepts redirect_from: - /code-security/supply-chain-security/understanding-your-software-supply-chain + - /code-security/concepts/supply-chain-security/automatic-dependabot-access-to-github-registries children: - supply-chain-security - open-source-license-compliance @@ -23,7 +24,6 @@ children: - dependabot-pull-requests - multi-ecosystem-updates - about-the-dependabot-yml-file - - automatic-dependabot-access-to-github-registries - dependabot-auto-triage-rules - dependabot-on-actions - dependabot-job-logs diff --git a/content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries.md b/content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries.md index 6cead7fd3caa..745f5e96847a 100644 --- a/content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries.md +++ b/content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries.md @@ -81,19 +81,6 @@ Any private registries used by the build must also be accessible to the workflow When you configure access to one or more private registries, {% data variables.product.prodname_dependabot %} can propose pull requests to upgrade a vulnerable dependency or to maintain a dependency, see [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-access-to-private-registries) and [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-private-registries). -{% ifversion org-automatic-registry-access %} - -### Automatic access to {% data variables.product.github %}-hosted registries - -For packages stored in {% data variables.product.prodname_registry %} and {% data variables.product.prodname_container_registry %}, {% data variables.product.prodname_dependabot %} can authenticate automatically without {% data variables.product.pat_generic_plural %} or `dependabot.yml` registry configuration. - -{% data variables.product.prodname_dependabot %} uses its `GITHUB_TOKEN` to request read access, reusing the same package access grants that {% data variables.product.prodname_actions %} workflows use. - -To enable this, grant the repository **Read** access to each package in the package settings. Once access is granted, {% data variables.product.prodname_dependabot %} can pull from those packages automatically, and you can remove any {% data variables.product.pat_generic %}-based registry entries you previously configured for them. - -See [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-access-to-private-registries#configuring-private-github-hosted-registries). -{% endif %} - {% ifversion org-private-registry-oidc %} ### Configuring OIDC authentication for a private registry diff --git a/content/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-access-to-private-registries.md b/content/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-access-to-private-registries.md index 2ed00dca94b7..34d0ec696d78 100644 --- a/content/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-access-to-private-registries.md +++ b/content/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-access-to-private-registries.md @@ -29,41 +29,8 @@ For specific ecosystems, you can configure {% data variables.product.prodname_de {% ifversion dependabot-on-actions-self-hosted %}To allow {% data variables.product.prodname_dependabot %} access to registries hosted privately or restricted to internal networks, configure {% data variables.product.prodname_dependabot %} to run on {% data variables.product.prodname_actions %} self-hosted runners. For more information, see [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-on-self-hosted-runners).{% endif %} -{% ifversion org-automatic-registry-access %} - -## Configuring private {% data variables.product.github %}-hosted registries - -For packages stored in {% data variables.product.prodname_registry %} or {% data variables.product.prodname_container_registry %}, {% data variables.product.prodname_dependabot %} can authenticate automatically using its `GITHUB_TOKEN`. This uses the same "Manage Actions access" grants that {% data variables.product.prodname_actions %} workflows use. No {% data variables.product.pat_generic_plural %} or `dependabot.yml` registry entries are required. - -The `dependabot.yml` registry configuration using {% data variables.product.pat_generic_title_case %}-based registry entries and described in [Configuring private third-party registries](#configuring-private-third-party-registries) is still required for third-party private registries (such as Artifactory, Azure Artifacts, or Nexus). - -To grant {% data variables.product.prodname_dependabot %} access to a private package: - - {% data reusables.package_registry.package-settings-from-org-level %} - {% data reusables.package_registry.package-settings-option %} - {% data reusables.package_registry.package-settings-actions-access %} - 1. {% data reusables.package_registry.package-settings-add-repo %}. - Search for the repository where {% data variables.product.prodname_dependabot %} runs, and select it. - {% data reusables.package_registry.package-settings-actions-access-role-repo %} - Select **Read** as the access level. {% data variables.product.prodname_dependabot %} only needs read access to pull packages. - -You need to repeat these steps for each private package that you want {% data variables.product.prodname_dependabot %} to access. - -Once access is granted, {% data variables.product.prodname_dependabot %} can pull from those packages automatically. You can remove any {% data variables.product.pat_generic %}-based registry entries in `dependabot.yml` that you previously configured for these packages. - -> [!NOTE] -> This method works for every {% data variables.product.prodname_registry %} ecosystem that {% data variables.product.prodname_dependabot %} supports, including container images in {% data variables.product.prodname_container_registry %}. - -For more information about how automatic access works, see [AUTOTITLE](/code-security/concepts/supply-chain-security/automatic-dependabot-access-to-github-registries). For more information about package access settings, see [AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package). - -## Configuring private third-party registries - -{% else %} - ## Configuring private registries -{% endif %} - {% ifversion org-private-registry %} You can configure {% data variables.product.prodname_dependabot %}'s access to private registries at the org-level. diff --git a/content/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-private-registries.md b/content/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-private-registries.md index 64448b57a25d..ae2fd86a0df5 100644 --- a/content/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-private-registries.md +++ b/content/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-private-registries.md @@ -109,12 +109,6 @@ The snippet below shows a `dependabot.yml` file configuration that uses a token. Docker supports using a username and password for registries. For more information, see `docker-registry` in [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-access-to-private-registries#docker-registry). -{% ifversion org-automatic-registry-access %} - -For images stored in {% data variables.product.prodname_container_registry %}, you can grant your repository **Read** access in the package settings instead of configuring credentials in your `dependabot.yml` file. See [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-access-to-private-registries#configuring-private-github-hosted-registries). - -{% endif %} - Snippet of `dependabot.yml` file using a username and password. {% raw %} diff --git a/content/copilot/reference/ai-models/model-hosting.md b/content/copilot/reference/ai-models/model-hosting.md index 64d1f3bfddbf..747e63f4df90 100644 --- a/content/copilot/reference/ai-models/model-hosting.md +++ b/content/copilot/reference/ai-models/model-hosting.md @@ -71,13 +71,11 @@ When using {% data variables.copilot.copilot_claude %}, input prompts and output Used for: -* {% data variables.copilot.copilot_gemini_25_pro %} -* {% data variables.copilot.copilot_gemini_3_flash %} * {% data variables.copilot.copilot_gemini_31_pro %} * {% data variables.copilot.copilot_gemini_35_flash %} * {% data variables.copilot.copilot_gemini_36_flash %} -{% data variables.product.prodname_copilot %} uses {% data variables.copilot.copilot_gemini_31_pro %}, {% data variables.copilot.copilot_gemini_3_flash %}, and {% data variables.copilot.copilot_gemini_25_pro %} hosted on Google Cloud Platform (GCP). When using {% data variables.copilot.copilot_gemini %} models, prompts and metadata are sent to GCP, which makes the [following data commitment](https://cloud.google.com/vertex-ai/generative-ai/docs/data-governance): _{% data variables.copilot.copilot_gemini %} doesn't use your prompts, or its responses, as data to train its models._ +{% data variables.product.prodname_copilot %} uses {% data variables.copilot.copilot_gemini %} models hosted on Google Cloud Platform (GCP). When using {% data variables.copilot.copilot_gemini %} models, prompts and metadata are sent to GCP, which makes the [following data commitment](https://cloud.google.com/vertex-ai/generative-ai/docs/data-governance): _{% data variables.copilot.copilot_gemini %} doesn't use your prompts, or its responses, as data to train its models._ To provide better service quality and reduce latency, {% data variables.product.github %} uses [prompt caching](https://cloud.google.com/vertex-ai/generative-ai/docs/data-governance#customer_data_retention_and_achieving_zero_data_retention). diff --git a/content/copilot/reference/ai-models/supported-models.md b/content/copilot/reference/ai-models/supported-models.md index cb4dd7202cc5..08ee0de02638 100644 --- a/content/copilot/reference/ai-models/supported-models.md +++ b/content/copilot/reference/ai-models/supported-models.md @@ -134,7 +134,6 @@ Some {% data variables.product.prodname_copilot_short %} models require minimum | Model | {% data variables.product.prodname_vscode %} | {% data variables.product.prodname_vs %} | JetBrains IDEs | Xcode | Eclipse | |----------------------------------------------------------|----------------------------------------------|------------------------------------------|----------------|-------|---------| -| {% data variables.copilot.copilot_gemini_3_flash %} | `v1.115.0` | `17.14.22` or `18.1.0` | `1.5.62` | `0.46.0` | `0.14.0` | | {% data variables.copilot.copilot_gemini_31_pro %} | `v1.115.0` | `17.14.22` or `18.1.0` | `1.5.62` | `0.46.0` | `0.14.0` | | {% data variables.copilot.copilot_gemini_35_flash %} | `v1.115.0` | `17.14.22` or `18.1.0` | `1.5.62` | `0.46.0` | `0.14.0` | | {% data variables.copilot.copilot_gemini_36_flash %} | `v1.128.0` | `17.14.22` or `18.1.0` | TBD | TBD | TBD | diff --git a/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md index afc9fdf4dfd4..fcdf731f451c 100644 --- a/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md +++ b/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md @@ -116,12 +116,6 @@ The specified repository does not need to be the repository where the source cod If you publish a package that is linked to a repository, {% data variables.product.prodname_actions %} workflows in the linked repository automatically get access to the package, unless your organization has disabled the automatic inheritance of access permissions. For more information, see [About inheritance of access permissions](#about-inheritance-of-access-permissions) above. {% endif %} -{% ifversion org-automatic-registry-access %} - -Granting a repository access here also allows {% data variables.product.prodname_dependabot %} to pull from this package automatically, without requiring {% data variables.product.pat_generic_plural %} or `dependabot.yml` registry configuration. See [AUTOTITLE](/code-security/concepts/supply-chain-security/automatic-dependabot-access-to-github-registries). - -{% endif %} - > [!NOTE] > * Syncing your package with a repository {% data variables.package_registry.package-settings-actions-access-menu %} is different than connecting your package to a repository. For more information about linking a repository to your package, see [AUTOTITLE](/packages/learn-github-packages/connecting-a-repository-to-a-package). > * You can choose to limit permissions to workflow jobs using the `permissions` key and `packages` scope. For more information, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token#modifying-the-permissions-for-the-github_token). diff --git a/content/pull-requests/get-started/about-stacked-prs.md b/content/pull-requests/get-started/about-stacked-prs.md index 721aa1e53601..704a9cf79c28 100644 --- a/content/pull-requests/get-started/about-stacked-prs.md +++ b/content/pull-requests/get-started/about-stacked-prs.md @@ -113,7 +113,7 @@ You can merge your entire stack, a single pull request, or a portion of the stac Stacks support merge commit, squash, and rebase merge methods, and they are merge-queue aware. The resulting commit history is the same as merging each pull request individually, starting from the bottom. > [!NOTE] -> If you merge via the API and want to use stacked pull requests, you'll need to update to use the new merge API for stacks. See [AUTOTITLE](/pull-requests/reference/stacked-pull-requests-rest-and-graphql-apis). +> If you merge via the API and want to use stacked pull requests, you'll need to update to use the new merge API for stacks. See [AUTOTITLE](/rest/pulls/pulls?apiVersion=2026-03-10#merge-a-pull-request-asynchronously). ## Next steps diff --git a/content/pull-requests/how-tos/merge-and-close-pull-requests/merging-stacked-pull-requests.md b/content/pull-requests/how-tos/merge-and-close-pull-requests/merging-stacked-pull-requests.md index 4a192de8bb3e..85b006b9dd4c 100644 --- a/content/pull-requests/how-tos/merge-and-close-pull-requests/merging-stacked-pull-requests.md +++ b/content/pull-requests/how-tos/merge-and-close-pull-requests/merging-stacked-pull-requests.md @@ -27,7 +27,7 @@ The merge box for a stacked pull request shows the status of the entire stack, n If the stack is not linear, for example, after changes were pushed to a lower branch or after the trunk moved ahead, a **Rebase stack** button will appear in the merge box and you'll need to rebase the stack before you can merge. > [!NOTE] -> * If you merge via the API and want to use stacked pull requests, you'll need to update your code to use the new merge API for stacks. See [AUTOTITLE](/pull-requests/reference/stacked-pull-requests-rest-and-graphql-apis). +> * If you merge via the API and want to use stacked pull requests, you'll need to update your code to use the new merge API for stacks. See [AUTOTITLE](/rest/pulls/pulls?apiVersion=2026-03-10#merge-a-pull-request-asynchronously). > * Auto-merge is not supported for stacked pull requests. ## Merging using a merge queue diff --git a/content/pull-requests/reference/stacked-pull-requests-rest-and-graphql-apis.md b/content/pull-requests/reference/stacked-pull-requests-rest-and-graphql-apis.md index 688069ed988b..3e1d0812e2ba 100644 --- a/content/pull-requests/reference/stacked-pull-requests-rest-and-graphql-apis.md +++ b/content/pull-requests/reference/stacked-pull-requests-rest-and-graphql-apis.md @@ -24,7 +24,7 @@ The REST API exposes stacked pull requests in two ways: * **The Stacks API.** A dedicated set of endpoints to list, read, create, extend, and dissolve stacks. This is the surface for creating and modifying stacks. > [!NOTE] -> If you merge via the API and want to use stacked pull requests, you'll need to update your code to use the new merge API for stacks. +> If you merge via the API and want to use stacked pull requests, you'll need to update your code to use the new merge API for stacks. See [AUTOTITLE](/rest/pulls/pulls?apiVersion=2026-03-10#merge-a-pull-request-asynchronously). For endpoints, parameters, and schemas, see [AUTOTITLE](/rest/pulls/pulls). diff --git a/content/rest/using-the-rest-api/troubleshooting-the-rest-api.md b/content/rest/using-the-rest-api/troubleshooting-the-rest-api.md index 23441fc7a896..126d87219982 100644 --- a/content/rest/using-the-rest-api/troubleshooting-the-rest-api.md +++ b/content/rest/using-the-rest-api/troubleshooting-the-rest-api.md @@ -73,6 +73,8 @@ You should also check for typos in your URL. For example, adding a trailing slas Additionally, any path parameters must be URL encoded. For example, any slashes in the parameter value must be replaced with `%2F`. If you don't properly encode any slashes in the parameter name, the endpoint URL will be misinterpreted. +You should also confirm that you are using an HTTP method that the endpoint supports. If you send a request with an HTTP method that the endpoint does not support, you will receive a `404 Not Found` response instead of `405 Method Not Allowed`. For example, sending a `DELETE` request to an endpoint that only supports `GET` will result in a `404 Not Found` response. You can refer to the reference documentation for the endpoint to confirm the supported HTTP method. + ## Missing results Most endpoints that return a list of resources support pagination. For most of these endpoints, only the first 30 resources are returned by default. In order to see all of the resources, you need to paginate through the results. For more information, see [AUTOTITLE](/rest/using-the-rest-api/using-pagination-in-the-rest-api). diff --git a/content/rest/using-the-rest-api/using-pagination-in-the-rest-api.md b/content/rest/using-the-rest-api/using-pagination-in-the-rest-api.md index 4d9b3bf18add..01e66579e9e6 100644 --- a/content/rest/using-the-rest-api/using-pagination-in-the-rest-api.md +++ b/content/rest/using-the-rest-api/using-pagination-in-the-rest-api.md @@ -66,6 +66,8 @@ The URLs in the `link` header use query parameters to indicate which page of res If an endpoint supports the `per_page` query parameter, then you can control how many results are returned on a page. For more information about query parameters see [AUTOTITLE](/rest/using-the-rest-api/getting-started-with-the-rest-api#query-parameters). +For most endpoints, the maximum value of `per_page` is `100`. If you specify a value greater than the maximum, {% data variables.product.company_short %} does not return an error. Instead, the value is automatically reduced to the maximum, and the response includes no more than the maximum number of results per page. Because the request still succeeds, you may receive fewer results than you expect without any indication that the `per_page` value was reduced. To confirm the default and maximum `per_page` values for an endpoint, see the reference documentation for that endpoint. + For example, this request uses the `per_page` query parameter to return two items per page: ```shell diff --git a/data/tables/copilot/annual-subscriber-model-multipliers.yml b/data/tables/copilot/annual-subscriber-model-multipliers.yml index a3f39a81f85f..e3ae65a67fd9 100644 --- a/data/tables/copilot/annual-subscriber-model-multipliers.yml +++ b/data/tables/copilot/annual-subscriber-model-multipliers.yml @@ -26,12 +26,6 @@ - model: 'Claude Sonnet 4.6' new_multiplier: '9' -- model: 'Gemini 2.5 Pro' - new_multiplier: '1' - -- model: 'Gemini 3 Flash' - new_multiplier: '0.33' - - model: 'Gemini 3 Pro' new_multiplier: '6' diff --git a/data/tables/copilot/model-comparison.yml b/data/tables/copilot/model-comparison.yml index 2dd27224de33..47ed672ee986 100644 --- a/data/tables/copilot/model-comparison.yml +++ b/data/tables/copilot/model-comparison.yml @@ -95,16 +95,6 @@ further_reading: '[Claude Sonnet 5 model card](https://www-cdn.anthropic.com/9e6a1044980d8c4ed85669faf9c2a8342e2e9f1e/Claude%20Sonnet%205%20System%20Card.pdf)' # Google -- name: Gemini 2.5 Pro - task_area: Deep reasoning and debugging - excels_at: Complex code generation, debugging, and research workflows - further_reading: '[Gemini 2.5 Pro model card](https://storage.googleapis.com/model-cards/documents/gemini-2.5-pro.pdf)' - -- name: Gemini 3 Flash - task_area: Fast help with simple or repetitive tasks - excels_at: Fast, reliable answers to lightweight coding questions - further_reading: '[Gemini 3 Flash model card](https://storage.googleapis.com/deepmind-media/Model-Cards/Gemini-3-Flash-Model-Card.pdf)' - - name: Gemini 3.1 Pro task_area: Deep reasoning and debugging excels_at: Effective and efficient edit-then-test loops with high tool precision diff --git a/data/tables/copilot/model-deprecation-history.yml b/data/tables/copilot/model-deprecation-history.yml index b1366710b097..a1967a15c88c 100644 --- a/data/tables/copilot/model-deprecation-history.yml +++ b/data/tables/copilot/model-deprecation-history.yml @@ -11,6 +11,14 @@ # - retirement_date: The official retirement date for the model (YYYY-MM-DD). # - suggested_alternative: The model recommended for migration. +- name: 'Gemini 2.5 Pro' + retirement_date: '2026-07-31' + suggested_alternative: 'Gemini 3.1 Pro' + +- name: 'Gemini 3 Flash' + retirement_date: '2026-07-31' + suggested_alternative: 'Gemini 3.6 Flash' + - name: 'Claude Opus 4.6 (fast mode) (preview)' retirement_date: '2026-06-29' suggested_alternative: 'Claude Opus 4.8 (fast mode) (preview)' diff --git a/data/tables/copilot/model-release-status.yml b/data/tables/copilot/model-release-status.yml index 9a1eb8f45174..e1823e4e26e3 100644 --- a/data/tables/copilot/model-release-status.yml +++ b/data/tables/copilot/model-release-status.yml @@ -99,14 +99,6 @@ # Google models -- name: 'Gemini 2.5 Pro' - provider: 'Google' - release_status: 'GA' - -- name: 'Gemini 3 Flash' - provider: 'Google' - release_status: 'Public preview' - - name: 'Gemini 3.1 Pro' provider: 'Google' release_status: 'Public preview' diff --git a/data/tables/copilot/model-supported-clients.yml b/data/tables/copilot/model-supported-clients.yml index 99701c355e7d..a830a66aaa0a 100644 --- a/data/tables/copilot/model-supported-clients.yml +++ b/data/tables/copilot/model-supported-clients.yml @@ -113,24 +113,6 @@ xcode: true jetbrains: true -- name: Gemini 2.5 Pro - dotcom: false - cli: false - vscode: true - vs: true - eclipse: true - xcode: true - jetbrains: true - -- name: Gemini 3 Flash - dotcom: false - cli: false - vscode: true - vs: true - eclipse: true - xcode: true - jetbrains: true - - name: Gemini 3.1 Pro dotcom: false cli: true diff --git a/data/tables/copilot/model-supported-plans.yml b/data/tables/copilot/model-supported-plans.yml index 36215c2eabf8..66a691613372 100644 --- a/data/tables/copilot/model-supported-plans.yml +++ b/data/tables/copilot/model-supported-plans.yml @@ -89,20 +89,6 @@ business: true enterprise: true -- name: Gemini 2.5 Pro - pro: true - pro_plus: true - max: true - business: true - enterprise: true - -- name: Gemini 3 Flash - pro: true - pro_plus: true - max: true - business: true - enterprise: true - - name: Gemini 3.1 Pro pro: true pro_plus: true diff --git a/data/tables/copilot/models-and-pricing.yml b/data/tables/copilot/models-and-pricing.yml index b33e21aefd91..59277ae9d0d4 100644 --- a/data/tables/copilot/models-and-pricing.yml +++ b/data/tables/copilot/models-and-pricing.yml @@ -268,26 +268,6 @@ cache_write: $12.50 # Google -- model: 'Gemini 2.5 Pro' - provider: google - release_status: GA - category: Powerful - threshold: 'Not applicable' - tier: 'Default' - input: $1.25 - cached_input: $0.125 - output: $10.00 - -- model: 'Gemini 3 Flash' - provider: google - release_status: Public preview - category: Lightweight - threshold: 'Not applicable' - tier: 'Default' - input: $0.50 - cached_input: $0.05 - output: $3.00 - - model: 'Gemini 3.1 Pro' provider: google release_status: Public preview diff --git a/src/graphql/data/fpt/changelog.json b/src/graphql/data/fpt/changelog.json index 7e4fcc78776a..679fbeac8b33 100644 --- a/src/graphql/data/fpt/changelog.json +++ b/src/graphql/data/fpt/changelog.json @@ -1,4 +1,17 @@ [ + { + "schemaChanges": [ + { + "title": "The GraphQL schema includes these changes:", + "changes": [ + "

Enum value GITLAB was added to enum MigrationSourceType

" + ] + } + ], + "previewChanges": [], + "upcomingChanges": [], + "date": "2026-07-31" + }, { "schemaChanges": [ { diff --git a/src/graphql/data/fpt/schema-migrations.json b/src/graphql/data/fpt/schema-migrations.json index 97b149aa1e24..3a408ef68c41 100644 --- a/src/graphql/data/fpt/schema-migrations.json +++ b/src/graphql/data/fpt/schema-migrations.json @@ -898,6 +898,10 @@ { "name": "GITHUB_ARCHIVE", "description": "

A GitHub Migration API source.

" + }, + { + "name": "GITLAB", + "description": "

A GitLab migration source.

" } ], "category": "migrations" diff --git a/src/graphql/data/fpt/schema.docs.graphql b/src/graphql/data/fpt/schema.docs.graphql index dac4229a99b2..b58186b28b1d 100644 --- a/src/graphql/data/fpt/schema.docs.graphql +++ b/src/graphql/data/fpt/schema.docs.graphql @@ -26354,6 +26354,11 @@ enum MigrationSourceType @docsCategory(name: "migrations") { A GitHub Migration API source. """ GITHUB_ARCHIVE + + """ + A GitLab migration source. + """ + GITLAB } """ diff --git a/src/graphql/data/ghec/schema-migrations.json b/src/graphql/data/ghec/schema-migrations.json index 97b149aa1e24..3a408ef68c41 100644 --- a/src/graphql/data/ghec/schema-migrations.json +++ b/src/graphql/data/ghec/schema-migrations.json @@ -898,6 +898,10 @@ { "name": "GITHUB_ARCHIVE", "description": "

A GitHub Migration API source.

" + }, + { + "name": "GITLAB", + "description": "

A GitLab migration source.

" } ], "category": "migrations" diff --git a/src/graphql/data/ghec/schema.docs.graphql b/src/graphql/data/ghec/schema.docs.graphql index dac4229a99b2..b58186b28b1d 100644 --- a/src/graphql/data/ghec/schema.docs.graphql +++ b/src/graphql/data/ghec/schema.docs.graphql @@ -26354,6 +26354,11 @@ enum MigrationSourceType @docsCategory(name: "migrations") { A GitHub Migration API source. """ GITHUB_ARCHIVE + + """ + A GitLab migration source. + """ + GITLAB } """