Tracked tools & platforms
Every AI dev tool, model provider and platform we watch. Pick one to see its current state and full change history — pricing, rate limits, deprecations and model releases, all in one place.
- Models
-
Added nvidia/MiniMax-M2.7-DFlash model with other license type, available until 2026-06-16.
-
-
-
We will deprecate Gemini 2.5 Pro and Gemini 3 Flash across all GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions) on July 31st,… The post Upcoming deprecation of Gemini 2.5 Pro and Gemini 3 Flash appeared first on The GitHub Blog.
-
In June, we announced that we are retiring GitHub Models and closed it to new customers. We’re now sharing the timeline for the next step: GitHub Models will be fully… The post GitHub Models is being fully retired on July 30, 2026 appeared first on The GitHub Blog.
-
Dependabot no longer supports Python version 3.9, which has reached its end-of-life. If you continue to use Python 3.9, there’s a risk that Dependabot will not create pull requests to… The post Deprecation of Python 3.9 for Dependabot appeared first on The GitHub Blog.
-
- Models
-
Two new Granite models added: granite-4.0-h-350m and granite-4.1-8b with Apache 2.0 license and specified availability dates.
-
- PricingLimitsDeprecationsModels
-
Added deprecation timeline information for gemini-embedding-2 and embedding-2-preview models with specific dates.
-
Two new Gemini models released: gemini-omni-flash-preview in public preview for video generation, and gemini-3.1-flash-lite-image moved to general availability.
-
Google Gemini API pricing updated with new rates for multiple models including text output at $1.50/$9.00/$0.25/$0.125 per 1M tokens and video output at $17.50 per 1M tokens with image pricing at $30 per 1M tokens.
-
- Models
-
Microsoft Phi model catalog changed: removed chatbench-distilgpt2, added HARC models with different licenses and dates.
-
- PricingDeprecations
-
Pro and Teams plans reduced by 20% — Pro now $16/mo, Teams $32/user/mo
-
Changelog updated with new Team MCP marketplace integration features and organization group access controls for team marketplaces.
-
- DeprecationsModels
-
Leanstral updated to version 1.5 with code agent improvements for Lean 4 formal proof engineering and automated theorem proving.
-
- Models
-
Two Gemma model variants (t5gemma-l-l-prefixlm-it and t5gemma-l-l-ul2-it) were removed.
-
- PricingLimitsDeprecationsModels
-
New model variant claude-sonnet-5 added to available Anthropic models.
-
Claude 3.5 Sonnet model added with introductory pricing of $2/$10 per million tokens through August 31, 2026
-
Model deprecation and retirement timeline table reformatted with updated discontinuation dates and model mappings for claude-instant versions.
-
-
-
Deprecation date: April 10, 2026 End of life date: September 27, 2026 The legacy Registrar domain management endpoints are deprecated and will reach their end of life on September 27, 2026. These endpoints have been replaced by the new Registrar API, which provides domain search, availability checking, and registration capabilities. Deprecated APIs: GET /accounts/{account_id}/registrar/domains — List domains GET /accounts/{account_id}/registrar/domains/{domain_name} — Get domain PUT /accounts/{a
-
Deprecation date: April 23, 2025 End of life date: September 15, 2026 The Zone Settings Batch API endpoints, which read and edit multiple zone settings in a single request, are deprecated and will reach their end of life on September 15, 2026. Use the per-setting endpoints to read and edit individual zone settings instead. Deprecated APIs: GET /zones/{zone_id}/settings PATCH /zones/{zone_id}/settings Replacements: Get zone setting — GET /zones/{zone_id}/settings/{setting_id} Edit zone setting —
-
Deprecation date: November 3, 2025 End of life date: July 15, 2026 The Gateway Audit SSH action for network policies is deprecated and will be fully removed on July 15, 2026. SSH with Access for Infrastructure is the replacement for managing and auditing SSH access. Creating new Gateway rules with action: "audit_ssh" via the dashboard was disabled in December 2024. Creating new rules via the API and Terraform was disabled on November 3, 2025. Editing existing rules via the dashboard, API, and Te
-
Deprecation date: March 19, 2026 End of life date: September 30, 2026 Service Key authentication for the Cloudflare API is deprecated and will be removed on September 30, 2026. API Tokens are capable of providing all functionality of Service Keys, with additional support for fine-grained permission scoping, expiration, and IP address restrictions. Deprecated behavior: Authenticating API requests using the X-Auth-User-Service-Key header. Generating new Service Keys via the Cloudflare dashboard or
-
Deprecation date: January 23, 2026 End of life date: June 30, 2026 Changing the type of an existing DNS record via the API is deprecated and will no longer be supported after June 30, 2026. Changing a DNS record's type is not a natural update operation and typically also requires changing the record's content. Updates to attributes such as name, TTL, or content are common and safe, but changing the record type introduces additional validation complexity and consistency risks. To align with corre
-
Deprecation date: December 9, 2025 End of life date: December 1, 2026 The following REST APIs are deprecated and will reach their end of life on December 1, 2026. DNS Analytics API DNS Firewall Analytics API All existing functionality is fully supported by Cloudflare's GraphQL Analytics API, which provides improved performance, flexibility, and long-term support. Integrations using the REST API need to be migrated to the new GraphQL API before December 1, 2026 in order to ensure uninterrupted se
-
End of life date: November 11, 2025 We are changing the definition of Devices. Devices are going to represent the real-world machines while the relation between Users and Devices will be represented by a new concept - Registrations. As a result multiple fields are moving from Devices to Registrations and we are deprecating the endpoints listed below. The deprecated endpoints are not supported on accounts with multi-user mode enabled. Deprecated API: GET /accounts/{account_id}/devices GET /accoun
-
Deprecation date: November 2025 End of life date: January 2026 Following on from the deprecation of Cloudflare Mirage, the following API endpoints that manage Mirage settings are now deprecated and will be sunsetted in January 2026. Deprecated APIs: GET /zones/{zone_id}/settings/mirage PATCH /zones/{zone_id}/settings/mirage Affected APIs: GET /zones/{zone_id}/pagerules/settings - Mirage will be removed from available settings. POST /zones/{zone_id}/pagerules - Mirage parameter will be removed. P
-
Deprecation date: October 15, 2025 End of life date: April 15, 2026 The Radar API currently has multiple summary and timeseries groups endpoints per dataset (for example, /radar/http/summary/device_type and /radar/http/timeseries_groups/device_type), which share nearly identical parameters and schema. To simplify the API and improve maintainability, these endpoints will be replaced with parameterized endpoints using a {dimension} path parameter. Deprecated APIs: GET /radar/http/summary/device_ty
-
Deprecation date: July 1, 2025 End of life date: January 1, 2026 The Radar Verified Bots API is now deprecated and will be replaced by the new Bots API. Deprecated APIs: GET /radar/verified_bots/top/bots GET /radar/verified_bots/top/categories Replacements: GET /radar/bots/summary/bot GET /radar/bots/summary/category
-
Deprecation date: July 1, 2025 The Cloudflare DWeb Resolver experiment is ending. Deprecated APIs: DoH resolver on resolver.cloudflare-eth.com
-
Deprecation date: June 15, 2025 The Rate Limiting API is deprecated, in favor of using the Rulesets API for managing the new rate limiting rules. Refer to Rate limiting (previous version) upgrade for more information about this change. Deprecated API: GET /zones/:zone_id/rate_limits POST /zones/:zone_id/rate_limits GET /zones/:zone_id/rate_limits/:rate_limit_id PUT /zones/:zone_id/rate_limits/:rate_limit_id DELETE /zones/:zone_id/rate_limits/:rate_limit_id Replacement: Rate limiting rules (new v
-
Deprecation date: June 15, 2025 The APIs for managing WAF managed rules (previous version) — namely for managing packages, rule groups, rules, and overrides — are deprecated in favor of using the Rulesets API for managing the new version of WAF Managed Rules. Refer to WAF Managed Rules upgrade for more information about this change. Deprecated APIs: GET /zones/:zone_id/firewall/waf/packages GET /zones/:zone_id/firewall/waf/packages/:package_id PATCH /zones/:zone_id/firewall/waf/packages/:package
-
Deprecation date: June 15, 2025 The Firewall Rules API and the Filters API are deprecated, since Firewall Rules was deprecated in favor of WAF custom rules. Refer to Firewall Rules upgrade for more information about this change. Deprecated APIs: GET /zones/:zone_id/firewall/rules POST /zones/:zone_id/firewall/rules PATCH /zones/:zone_id/firewall/rules PUT /zones/:zone_id/firewall/rules DELETE /zones/:zone_id/firewall/rules GET /zones/:zone_id/firewall/rules/:rule_id PATCH /zones/:zone_id/firewal
-
Deprecation date: June 8, 2025 The Zone Settings API endpoints for managing zone-level CNAME flattening are deprecated. Instead, use the Show DNS Settings and Update DNS Settings endpoints to manage this setting. Changes via the old endpoints will be reflected in the new ones, and vice versa, so there is no need to migrate existing zones. However, future API calls must use DNS Settings instead of the Zone Settings endpoints. Note that, with the deprecated zone setting, values "off" and "apex" ha
-
Deprecation date: March 23, 2025 Users can now add custom nameservers that are not part of a zone managed within their account. As a result, any zone is eligible for custom nameservers, regardless of whether it is managed by Cloudflare. Given this change, an endpoint to check for eligible zones is no longer relevant and is therefore being deprecated. Deprecated APIs: GET /accounts/:account_id/custom_ns/availability
-
Deprecation date: March 20, 2025 End of life date: September 20, 2025 The /top/industry and /top/vertical attack endpoints are now deprecated and will be replaced by the corresponding summary endpoints. Affected APIs: GET /radar/attacks/layer3/top/industry GET /radar/attacks/layer3/top/vertical GET /radar/attacks/layer7/top/industry GET /radar/attacks/layer7/top/vertical Replacements: GET /radar/attacks/layer3/summary/industry GET /radar/attacks/layer3/summary/vertical GET /radar/attacks/layer7/
- Deprecation API deprecations - Security Center: Security level and Threat Score are now automated 1y ago
Change date: March 17, 2025 Cloudflare now combines the IP address threat signal with threshold and botnet data, no longer requiring you to set a sensitivity level. Users will no longer be able to set Security level via the Cloudflare dashboard. However, users can still rely on the existing API or Terraform configuration to set a Security level. If you are using threat score in rule expressions, you should review those expressions to make sure the rule still triggers when appropriate. Cloudflare
- Deprecation API deprecations - Account Settings: default_nameservers and use_account_custom_ns_by_default 1y ago
Deprecation date: March 14, 2025 The fields "default_nameservers" and "use_account_custom_ns_by_default" within the "settings" object of accounts are deprecated. Instead, use the Show DNS Settings and Update DNS Settings endpoints to manage this setting. This setting is available in the new API as.zone_defaults.nameservers.type, with allowed values "cloudflare.standard", "cloudflare.standard.random", "custom.account" and "custom.tenant". Changes via the old endpoints will be reflected in the ne
-
Deprecation date: March 11, 2025 End of life date: June 11, 2025 The layer 7 attack magnitude query parameter, which allows you to define attack magnitude by total requests mitigated (MITIGATED_REQUESTS) or total zones attacked (AFFECTED_ZONES), is deprecated. Moving forward, Cloudflare Radar will only support defining layer 7 attack magnitude based on the total number of mitigated requests. Affected API: GET /radar/attacks/layer7/top/attacks Replacement: Users should stop using the magnitude pa
-
Deprecation date: February 21, 2025 The following URL parameters for filtering DNS records are deprecated: name=contains:value Instead, use the supported name.contains=value syntax. name=starts_with:value Instead, use the supported name.startswith=value syntax. name=ends_with:value Instead, use the supported name.endswith=value syntax. name=one,two,three (searching for one of multiple possible names, separated by commas) Instead, make multiple requests, one for each possible name. Alternatively,
-
Deprecation date: November 21, 2025 The self_hosted_domains field for Access applications is deprecated in favor of destinations to allow for more flexibility in defining different types of domains. Before: { //... "self_hosted_domains": ["foo.example.com", "bar.example.com"] } After: { //... "destinations": [ { "type": "public", "uri": "foo.example.com" }, { "type": "public", "uri": "bar.example.com" } ] } The API will accept both fields until the deprecation date. If self_hosted_domains are
-
Deprecation date: November 30, 2024 Currently, each individual DNS record returned by the API contains information about the zone it is on, specifically the zone ID and name. { "result": [ { //... "zone_id": "ab922473c42f4e50819d7c1c9b81b16b", "zone_name": "example.com" } ], //... } This information is redundant because both affected API routes are already within the zone scope. In particular, the zone ID will already be known to any user of these routes because it appears in the URL. The zone
-
Deprecation date: October 1, 2024 Cloudflare is making a minor change to the representation of certain errors when creating DNS records. Currently, when the DNS record to be created is invalid, an error similar to the following may be returned: { "result": null, "success": false, "errors": [ { "code": 1004, "message": "DNS Validation Error", "error_chain": [ { "code": 9999, "message": "This is an example." } ] } ], "messages": [] } After October 1st, 2024, the error_chain will be omitted, return
-
Deprecation date: September 13, 2024 The dedicated endpoints for DNS settings use_apex_ns and secondary_overrides are being deprecated. Instead, use the Show DNS Settings and Update DNS Settings endpoints to manage these settings. Instead of the.../use_apex_ns endpoint, use the multi_provider field. Instead of the.../secondary_overrides endpoint, use the secondary_overrides field. Deprecated APIs: GET /zones/:zone_id/dns_settings/use_apex_ns PATCH /zones/:zone_id/dns_settings/use_apex_ns GET /
-
- PricingModels
-
Removed deepseek-coder-6.7b-base model from available weights.
-
- PricingModels
-
Video pricing now covers 480p, 720p, and 1080p resolutions
-
- Models
-
Removed two Qwen3-VL-30B model variants (A3B-Instruct and A3B-Thinking) from availability.
-
- PricingLimitsDeprecationsModels
-
OpenAI pricing page now displays ChatGPT Business ($20/user/mo) and Enterprise plans instead of API token rates
-
On February 13, 2026, alongside the previously announced retirement of GPT‑5 (Instant, Thinking, and Pro), we will retire GPT‑4o, GPT‑4.1, GPT‑4.1 mini, and OpenAI o4-mini from ChatGPT. In the API, there are no changes at this time.
-
Nakasone brings cybersecurity experience to growing Board of Directors; will join the Board’s Safety and Security Committee
- Deprecation GPT-4 API general availability and deprecation of older models in the Completions API 2y ago
GPT-3.5 Turbo, DALL·E and Whisper APIs are also generally available, and we are releasing a deprecation plan for older models of the Completions API, which will retire at the beginning of 2024.
-
-
-
Edit 2026-06-13: Rollout date pushed from 2026-06-15 to 2026-06-29 to allow additional AMI build verification. No other changes to the rollout plan. Starting with pg_graphql 1.6.0 (shipping in new Supabase projects from 2026-06-29), GraphQL introspection is disabled by default. Who is affected New projects created on or after 2026-06-29 will run pg_graphql 1.6.0+ and have introspection disabled by default. Existing projects are not affected unless and until you upgrade pg_graphql to 1.6.0+ (e.g.
- Deprecation Self-hosted Supabase: switching Studio from supabase_admin to postgres (breaking change) 1mo ago
What's Changing? The week of June 15, 2026, the default docker-compose.yml in self-hosted Supabase will switch the database role used by Studio and postgres-meta from supabase_admin to postgres: studio.environment.POSTGRES_USER_READ_WRITE will default to postgres meta.environment.PG_META_DB_USER will default to postgres This aligns self-hosted Supabase with the platform behavior introduced in late 2022, which removed superuser access from the dashboard SQL editor and shifted ownership of user-cr
-
What's Changing? The week of June 15, 2026, the default db image in the self-hosted Supabase docker-compose.yml will move from Postgres 15 to Postgres 17. ⚠️ If your database uses timescaledb, plv8, plcoffee, or plls, you cannot upgrade to the Supabase images of PG 17 - these extensions are no longer included. This affects the default image tag only. Pinning to a specific supabase/postgres 15.x tag will continue to work, and the PG 15 images on Docker Hub will remain available. Existing Postgres
-
Supabase support for Postgres 14 is deprecated as of 1st July 2026 and support for it will be fully removed from this date on. All projects still on a deprecated Postgres version on the 1st July 2026 will automatically be upgraded to the latest Postgres version available. If extensions that are no longer supported are being used, the projects will be paused instead and no longer serve traffic. Why upgrade? Postgres 17 brings significant improvements to performance, security, and reliability. Dep
-
As part of our ongoing commitment to providing a secure and reliable experience for all developers, we will drop support for Node.js 20 in accordance with our Support Policy. Affected libraries All packages published from the supabase-js monorepo: @supabase/supabase-js @supabase/auth-js @supabase/realtime-js @supabase/functions-js @supabase/storage-js @supabase/postgrest-js Timeline End of Support for Node.js 20: June 30, 2026 Why? Node.js 20 reached its official end of life on April 30, 2026 (a
-
What's changing The /v1/oauth/token endpoint currently returns HTTP 201 Created on success. On May 26, 2026 June 1, 2026, this will change to HTTP 200 OK. Why OAuth 2.1 (section 3.2.3) mandates a 200 response from token endpoints. Returning 201 is non-compliant and has caused token exchange failures with some strict OAuth clients. Am I affected? You're only affected if your integration explicitly checks for a 201 status code from this endpoint. For example, the following popular client implement
-
New tables in the public schema will no longer be exposed to the Data API automatically. When this change takes effect Starting today (April 28, 2026), you can create new Supabase projects where tables in the public schema are not exposed to the Data API and GraphQL API by default. You can enable this setting at project creation. On May 18, 2026, pg_graphql will not be enabled by default. More details here. On May 30, 2026 this setting starts to become the default for all new projects. This will
-
What’s Changing? The Data API returns the full OpenAPI spec for any schema exposed to the Data API at the root path: https://[projectref].supabase.co/rest/v1/ Starting March 11, we will begin deprecating support for accessing this endpoint via the anon key. You will get the following error message if this endpoint is accessed via the anon key {"message":"Access to schema is forbidden","hint":"Accessing the schema via the Data API is only allowed using a secret API key."} The endpoint remains acc
- Deprecation Breaking Change: pg_graphql no longer enabled automatically (within approx 3 weeks from today) 5mo ago
In a forthcoming release within approximately 3 weeks, pg_graphql will be disabled by default on new Supabase projects. This change aligns pg_graphql with our security-first approach of minimizing exposed API surface area by default. Services and extensions that expose schema metadata are now opt-in rather than opt-out, reducing the default attack surface for new projects. Who is affected: New projects will no longer have pg_graphql enabled automatically Existing projects older than 30 days with
-
- Pricing
-
On June 30th, 2026, Vercel will remove support for the legacy cipher suite.DHE-RSA-AES256-GCM-SHA384 This cipher may still be used by automated systems, security scanners, and HTTP clients with non-standard TLS configurations. After this date, clients using TLS 1.2 will only be able to connect to the Vercel network with:our six remaining cipher suites Modern clients and TLS 1.3 connections are unaffected. If you operate integrations or automated systems that connect to a domain hosted on Vercel
-
Support for the legacy config file will be officially removed on. Migrate existing files by renaming them to no other content changes are required.now.jsonnow.jsonvercel.json,March 31st, 2026 For more advanced use cases, try for programmatic project configuration.vercel.ts Learn more about configuring projects with in the.vercel.jsondocumentation Read more
-
Team owners and members can now upgrade all projects using Node.js 18 or earlier to Node.js 22 with one click in the Vercel Dashboard. This updates the. If your project also defines a version in, you'll need to update it manually. Existing deployments are not affected.Node.js version in project settingspackage.json View and upgrade deprecated Node.js projects now. Read more
-
Node.js 18 (LTS support ends April 30, 2025) and the Vercel legacy build image will be deprecated on September 1, 2025. If you are still using the legacy build image on this date, new builds will display an error. What changes between the legacy build image and latest build image? How do I know if I am still using the legacy build image? Will my existing deployments be affected? Existing deployments However, the Node.js version will need to be updated on your next deployment.will not be affected
-
Following the Node.js 18 end of life on April 30, 2025, we are deprecating Node.js 18 for Builds and Functions on September 1, 2025. Will my existing deployments be affected? No, existing deployments with Serverless Functions will not be affected. When will I no longer be able to use Node.js 18? On September 1, 2025, Node.js 18 will be disabled in. Existing projects using 18 as the version for Functions will display an error when a new deployment is created.project settings How can I upgrade my
-
Following the Node.js 16 end of life on September 11, 2023, we are deprecating Node.js 16 for Builds and Functions on January 31, 2025. Will my existing deployments be affected? No, existing deployments with Serverless Functions will not be affected. When will I no longer be able to use Node.js 16? On January 31, 2025, Node.js 16 will be disabled in. Existing projects using 16 as the version for Functions will display an error when a new deployment is created.project settings How can I upgrade
-
This changelog entry is historical. Edge Functions are deprecated for new projects. Use with the Node.js runtime and. Use for request-time routing before a response completes.Note:Vercel FunctionsFluid computeRouting Middleware Requests received by Vercel Functions are now enriched with headers containing information about the timezone of the visitor: As an example, a request from Tokyo is now enriched with the following headers: This header is now automatically activated for all new and existi
-
This changelog entry is historical. Edge Functions are deprecated for new projects. Use with the Node.js runtime and. Use for request-time routing before a response completes.Note:Vercel FunctionsFluid computeRouting Middleware IP Geolocation is now available on all plans,, for requests received by Vercel Functions. Check out to learn more.Hobby, Pro and Enterprise teamsour documentation Read more
-
- ModelsOpen AI2 OLMo → current state & full history
- Open AWS → current state & full history
- PricingOpen Bolt.new → current state & full history
- PricingOpen GitHub Copilot → current state & full history
- PricingOpen Lovable → current state & full history
- ModelsOpen Meta Llama → current state & full history
- ModelsOpen MiniMax → current state & full history
- ModelsOpen Moonshot Kimi → current state & full history
- PricingOpen Replit → current state & full history
- PricingOpen Windsurf · Devin → current state & full history
- ModelsOpen Zhipu GLM → current state & full history
No tools match these filters.