Code scanning: CodeQL Action v2 is now deprecated

On December 13, 2023, we released CodeQL Action v3, which runs on the Node.js 20 runtime. In January 2024, we announced that CodeQL Action v2 would be deprecated at the same time as GitHub Enterprise Server (GHES) 3.11. This deprecation period has elapsed and CodeQL Action v2 is now discontinued. It will no longer be updated or supported, and while we will not be deleting it except in the case of a security vulnerability, workflows using it may eventually break. New CodeQL analysis capabilities will only be available to users of v3.

For more information about this deprecation, please see the original deprecation announcement from January 2024.

How does this affect me?

Default setup

Users of code scanning default setup do not need to take any action in order to automatically move to CodeQL Action v3.

Advanced setup

Users of code scanning advanced setup need to change their workflow files in order to start using CodeQL Action v3.

Users of GitHub.com and GitHub Enterprise Server 3.12 (and newer)

All users of GitHub code scanning (which by default uses the CodeQL analysis engine) on GitHub Actions on the following platforms should update their workflow files:

  • GitHub.com (including open source repositories, users of GitHub Teams and GitHub Enterprise Cloud)
  • GitHub Enterprise Server (GHES) 3.12 (and newer)

Users of the above-mentioned platforms should update their CodeQL workflow file(s) to refer to the new v3 version of the CodeQL Action. Note that the upcoming release of GitHub Enterprise Server 3.12 will ship with v3 of the CodeQL Action included.

Users of GitHub Enterprise Server 3.11 (and older)

GitHub Enterprise Server 3.11 (and older) is now deprecated. For more information on using the CodeQL Action on a deprecated GitHub Enterprise Server version, refer to the relevant sections of the CodeQL Action v2 deprecation announcement.

Exactly what do I need to change?

To upgrade to CodeQL Action v3, open your CodeQL workflow file(s) in the .github directory of your repository and look for references to:

  • github/codeql-action/init@v2
  • github/codeql-action/autobuild@v2
  • github/codeql-action/analyze@v2
  • github/codeql-action/upload-sarif@v2

These entries need to be replaced with their v3 equivalents:

  • github/codeql-action/init@v3
  • github/codeql-action/autobuild@v3
  • github/codeql-action/analyze@v3
  • github/codeql-action/upload-sarif@v3

Can I use Dependabot to help me with this upgrade?

Yes, you can! For more details on how to configure Dependabot to automatically upgrade your Actions dependencies, please see this page.

Secret scanning expands default pattern support

GitHub continually updates the default pattern set for secret scanning with new patterns and upgrades of existing patterns, ensuring your repositories have comprehensive detection for different secret types.

The following new patterns were added over the last few months. Secret scanning automatically detects any secrets matching these patterns in your repositories. See the full list of supported secrets in the documentation.

Provider Token Partner User Push protection
Anthropic anthropic_admin_api_key ✓ ✓ ✓
Asaas asaas_api_token ✓ ✓
Asana asana_legacy_format_personal_access_token  ✓ ✓
Azure azure_openai_key ✓ ✓ ✓
Azure microsoft_azure_common_annotated_security_key ✓
Azure microsoft_azure_entra_id_token ✓ ✓ ✓
Cfx.re cfxre_server_key ✓ ✓
Cockroach Labs ccdb_api_key ✓ ✓
Coveo coveo_access_token ✓ ✓
Databento databento_api_key ✓ ✓
Datastax datastax_astracs_token ✓ ✓ ✓
Google google_cloud_service_account_credentials ✓ ✓ ✓
Google google_gcp_api_key_bound_service_account ✓ ✓  
Hubspot hubspot_private_apps_user_token ✓ ✓
Hubspot hubspot_smtp_credential ✓ ✓
Hugging Face hf_user_access_token ✓ ✓ ✓
Iterative iterative_dvc_studio_access_token ✓ ✓
Lichess lichess_personal_access_token ✓ ✓
Lichess lichess_oauth_access_token ✓ ✓
MongoDB mongodb_atlas_db_uri_with_credentials ✓ ✓
Netflix netflix_netkey ✓ ✓
OpenRouter openrouter_api_key ✓ ✓
Oracle oracle_api_key ✓
Polar polar_access_token ✓ ✓
Polar polar_authorization_code ✓ ✓
Polar polar_client_registration_token ✓ ✓
Polar polar_client_secret ✓ ✓
Polar polar_personal_access_token ✓ ✓
Polar polar_refresh_token ✓ ✓
Replicate replicate_api_token ✓ ✓ ✓
Scalr scalr_api_token ✓ ✓ ✓
Sentry sentry_org_auth_token ✓
Sentry sentry_user_auth_token ✓
Sentry sentry_user_app_auth_token ✓
Sentry sentry_integration_token ✓
Shopee shopee_open_platform_partner_key ✓ ✓
Siemens siemens_api_token ✓ ✓ ✓
Sindri sindri_api_key ✓ ✓
Tailscale tailscale_api_key ✓ ✓

The following existing patterns were upgraded to be included in push protection. When push protection is enabled, secret scanning automatically blocks any pushes that contain a secret matching these patterns.

Provider Token
Contentful contentful_personal_access_token
GitLab gitlab_access_token
Ionic ionic_refresh_token
Orbit orbit_api_token
PyPI pypi_api_token
Thunderstore thunderstore_io_api_token
Yandex yandex_cloud_iam_access_secret

Learn more about securing your repositories with secret scanning.

See more

GitHub Models introduces JSON schema support for response formats

You can now specify a custom JSON schema as a response format, alongside the existing text and recently released general JSON option. When JSON schema is selected, an input box will allow you to define your desired schema format directly in the playground.

JSON Schema support in Models

This enhancement provides more control if you’re working with models that require structured responses, helping to mitigate issues like models outputting unnecessary tokens. You can either specify a single object or an array of objects. Additionally, you can save this JSON schema as a preset so that you can use it again later.

JSON Schema structured outputs are currently only supported for the GPT 4o model, and specifically for the api-version: “2024-08-01-preview”.

GitHub Models is a catalog and playground of AI models to help you build AI features and products. You can start using models for free with just your GitHub PAT.

Learn more about GitHub Models or join the conversation in our community discussions.

See more
View all changes