API Breaking Changes and Deprecations — April 2026

Auth0 is ending the Free Trial for the Mobile Driver’s License (mDL) Verification Service Early Access and will remove access for enrolled tenants after May 11, 2026. This impacts users who were part of the Early Access program.

Auth0 is ending the Free Trial for the Mobile Driver’s License (mDL) Verification Service Early Access and will remove access for enrolled tenants after May 11, 2026. This service will not be moved forward as part of the Auth0 product.

The Delegated Administration Extension has been updated to remove its dependency on the deprecated `enabled_clients` field on connections. Users of the extension should update to v4.8.3 to ensure compatibility with the upcoming deprecation of legacy management of a connection's enabled clients.

Service Key authentication has been deprecated. Additionally, new RFC 9440 mTLS certificate fields are now available in Workers, enhancing security and authentication options.

The `Install-Datadog.ps1` PowerShell script is deprecated and will be removed in a future version. Users should switch to `datadog-installer.exe` or the MSI installer for Windows Agent installations.

GitHub Copilot code review will begin consuming GitHub Actions minutes starting June 1, 2026. This change impacts users who rely on Copilot for code review and use GitHub Actions, as it will incur costs against their Actions minute allocation.

GitHub is deprecating several security-related fields in the organization API. Developers using these fields will need to update their integrations to avoid future issues.

GitHub has retired changes to Copilot plans for individuals and is sunsetting SHA-1 in HTTPS, which may impact users relying on these features.

Several GPT-5.1 Codex models (GPT-5.1 Codex, GPT-5.1-Codex-Max, and GPT-5.1-Codex-Mini) have been deprecated. Users should update their integrations to avoid future issues.

GitHub has retired Opus 4.6 Fast from Copilot Pro+ and is enforcing new limits. Additionally, new GitHub Copilot Pro trials are being paused. These changes indicate a reduction in available features and access for Copilot users.

The GPT-5.1 Codex, GPT-5.1-Codex-Max, and GPT-5.1-Codex-Mini models have been retired from GitHub Copilot. Users relying on these specific models should migrate to supported alternatives.

GitHub Copilot will deprecate Claude Sonnet 4. Users should be aware of this upcoming change and plan for potential impacts on their Copilot experience.

Strict act-as mode is now globally enforced for all Dataform repositories, requiring the use of a custom service account or user credentials for running Dataform workflows, BigQuery pipelines, notebooks, and data preparations. This is a breaking change that will require users to update their authentication configurations.

As of April 10, 2026, creating, running, and editing Gemini Cloud Assist investigations for AlloyDB for PostgreSQL and Cloud SQL instances (MySQL, PostgreSQL, SQL Server) will require a Premium Support contract. Existing investigation results remain accessible.

Gemini Cloud Assist has replaced the `cloudaicompanion.instances.completeTask` IAM permission with `geminicloudassist.agents.invoke`. Users with custom IAM roles for Gemini Cloud Assist must update their roles to maintain access.

Apigee X introduces a new IAM role, `apigee.coreServiceAgent`, which must be used instead of the `apigee.serviceAgent` role. This change is effective immediately and requires users to update their IAM policies to avoid potential service disruptions.

This release includes several breaking changes, such as the removal of the unused recurrence object in Enrich and the new mandatory `consumer_report_permissible_purpose` field for Plaid Check Consumer Report. It also deprecates the FinanceKit Sync API and CocoaPods integration for iOS SDK, while introducing new features like `cfi_code` in Investments and custom Signal Rules.

This release includes several breaking changes and deprecations. Notably, the `consumer_report_permissible_purpose` field is now required for Plaid Check Consumer Report, the FinanceKit sync API and CocoaPods integration are deprecated, and there are significant migrations for Stripe Charges and Sources API users and Bank of America API users. Additionally, the error object in webhooks now returns `display_message: null` instead of omitting the field.

Checkout metafields are deprecated as of API version 2026-04. Developers must migrate to cart metafields in checkout UI extensions and order metafields in customer account UI extensions to avoid future disruptions.

ShopifyQL analytics fields are deprecated and replaced with renamed versions (e.g., sales reversals) in API version 2026-04 to better reflect all order adjustments. Users must update their queries before the fields are removed.

The MetaobjectAdminAccess enums PRIVATE and PUBLIC_READ are being removed in July 2026. Developers using these enums will need to update their code to avoid breaking changes.

The MetaobjectAdminAccess enums PRIVATE and PUBLIC_READ are being removed from metaobject definitions in API version 2026-07. This is a breaking change that will affect applications using these enums.

The `grams` field in `DraftOrderLineItem` is being removed in API version 2026-07. Developers must replace `grams` with `weight` to avoid errors in future queries.

Shopify Scripts are being deprecated and will stop executing by June 30, 2026. Developers should migrate to Shopify Functions, which now support discounts, shipping, and payments, by April 15, 2026.

Shopify has deprecated checkout metafields as of API version 2026-04. Developers must migrate to cart metafields for checkout UI extensions and order metafields for customer account UI extensions to avoid future issues.

Checkout metafields are deprecated as of API version 2026-04. Developers should migrate to cart metafields in checkout UI extensions and order metafields in customer account UI extensions to avoid future issues.

The --force flag in Shopify CLI's `app release` command is deprecated and will be removed in May 2026 to prevent accidental app extension deletions. Developers should update CI/CD scripts to use --allow-updates for safer deployments.

The Stripe API has introduced several breaking changes, including updates to card property requirements, removal of deprecated methods, and renaming of attributes. Additionally, some capabilities and fields have been deprecated.

The Stripe API is introducing several breaking changes and deprecations, including updates to card property requirements, removal of deprecated methods, renaming of initialization methods, and changes to UI mode enum values. These changes will require updates to existing integrations to avoid failures.

The Stripe API has multiple breaking changes and deprecations across various products. Key changes include the removal of deprecated Payment Intents, Setup Intents, and Sources methods from Stripe.js, deprecation of alphanumeric_id for Issuing Authorization, and deprecation of the bank_transfer_payments capability type. Users should review the full changelog to identify all affected areas and plan for necessary migrations.

The Transit CallerID feature is being sunset. Users must migrate to Verified CallerID or Immutable Call Forwarding before May 31, 2026, to avoid service disruption.

The previous changelog mentioned 'OAuth for Twilio APIs is now in GA', but this entry has been removed in the new diff. This suggests a potential deprecation or removal of this announcement, which could impact users relying on this feature's general availability.

The Transit CallerID feature is sunsetting, requiring migration to Verified CallerID or Immutable Call Forwarding by May 31, 2026. Additionally, A2P 10DLC campaign registration will require privacy policy and terms & conditions URLs starting June 30, 2026.

The Transit CallerID feature is being sunset and users must migrate to Verified CallerID or Immutable Call Forwarding before May 31, 2026. This change will require action from users currently relying on Transit CallerID.

The Verify Events: Verification Stream (all versions) will no longer provide updated message delivery status or error code information. This change may impact users relying on this data for real-time message delivery insights.

Vercel Hobby plans will now have a maximum deployment retention policy of 30 days, automatically removing older deployments. This change, effective April 29th, will impact users on Hobby plans by deleting deployments outside this window, excluding the 10 most recent production deployments and aliased deployments.