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
-
NVIDIA-Nemotron-Parse-2.0 license changed from 'other' to 'openmdw-1.1'
-
- PricingLimitsDeprecationsModels
-
Model deprecation page restructured with navigation elements added and content reorganized, but core model status information preserved with same deprecation dates.
-
Introductory API token pricing for Claude 3.5 Sonnet expired; now at standard rates ($5 input / $25 output per 1M tokens)
-
Model claude-opus-4-1-20250805 was removed from the available Anthropic models.
-
- PricingModels
-
Added notice that not all models support Batch API requests, with details available on individual model pages.
-
- PricingModels
-
Concurrency limit raised to 3; cache-based pricing tiers removed
-
DeepSeek model changed from deepseek-coder-33b-base to DeepSeek-V4-Pro-0813 with updated license and date.
-
-
-
GitHub API: 5 additive changes
-
With the launch of MAI-Code-1.1-Flash, we will deprecate MAI-Code-1-Flash across all GitHub Copilot experiences on September 10, 2026: Model Deprecation date Suggested alternative MAI-Code-1-Flash 9-10-2026 MAI-Code-1.1-Flash Please update your workflows… The post Upcoming deprecation of MAI-Code-1-Flash appeared first on The GitHub Blog.
-
You’ll no longer be able to configure custom thread subscriptions for GitHub notifications. What’s changing As part of this rollout, GitHub will remove support for custom thread subscription settings. If… The post Custom thread subscriptions are being deprecated appeared first on The GitHub Blog.
-
We’ve retired the GitHub Copilot Billing Preview app, and it’s no longer available. You can review and manage your Copilot spend directly in your GitHub billing settings. The app helped… The post Retiring the Copilot Billing Preview app appeared first on The GitHub Blog.
-
Beginning August 4, 2026, GitHub Spark no longer accepts new users or allows the creation of new apps. Existing users can continue to access GitHub Spark until August 31, 2026… The post Upcoming deprecation of GitHub Spark on github.com appeared first on The GitHub Blog.
-
We will deprecate the following models across all GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions), on September 1st, 2026: Model Deprecation date… The post Upcoming August 2026 model deprecations in GitHub Copilot appeared first on The GitHub Blog.
-
As of today, July 31, 2026, we have deprecated the following models across all GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions). Model… The post Gemini 2.5 Pro and Gemini 3 Flash deprecated appeared first on The GitHub Blog.
-
As of July 30, 2026, GitHub Models is now retired. The playground, model catalog, inference API, and bring your own key (BYOK) are no longer available to any customer, including… The post GitHub Models is now retired appeared first on The GitHub Blog.
-
npm v12 is now generally available and tagged latest. This major release turns on the install-time security defaults we announced in June, and it’s also where we begin a deprecation… The post npm install-time security and GAT bypass2fa deprecation appeared first on The GitHub Blog.
-
The Copilot Billing Preview app will be retired on August 3, 2026. If you use it to review your GitHub Copilot spend, you can get even greater visibility directly in… The post Copilot Billing Preview app will be retired on August 3 appeared first on The GitHub Blog.
-
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.
-
- Pricing
-
Pro plan pricing reduced with new annual billing model and explicit parallel agent limits introduced
-
- Models
-
Removed six T5-Gemma model variants with gemma license dated 2025-06-19.
-
- PricingDeprecations
-
Aug 19, 2026 changelog added cloud agents and Cursor harness improvements including subscriptions, custom modes, subagents on isolated VMs, /goal command, and steering improvements.
-
Composer removed from Grok feature descriptions across Free, Pro, Pro+, Ultra, and Teams plans
-
- Pricing
-
Daily build credits grant now capped at 30 per month for some regional plans instead of unlimited daily 5 credits.
-
- Models
-
Qwen model offering changed from Qwen3-VL-4B-Instruct to Qwen3.8-27B with updated license expiration date.
-
- PricingLimitsDeprecationsModels
-
Added gemini-3.7-flash model with August 2026 release date and no announced shutdown date.
-
Gemini API pricing increases announced for January 1, 2027, with rates doubling for multiple models including Flash, Pro, and Sonnet variants.
-
Multiple model releases to GA and preview including Gemini 3.6 Flash, Gemini 3.5 Flash, Gemini 3.1 Flash-Lite, image/video generation models, and new Managed Agents with Antigravity Agent, plus several deprecation announcements with shutdown dates.
-
- DeprecationsModels
-
OCR service updated from version 4 to 4.1 with new features including paragraph-level bounding boxes, structural block labels, and block-level confidence scores.
-
- Pricing
-
Team owners and members can now upgrade all projects using Node.js 20 or earlier to Node.js 24 with one click from 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
-
Significant token pricing reductions across base and Pro models (up to 80% decrease on base input tokens)
-
Following the Node.js 20 end of life on April 30, 2026, we are deprecating Node.js 20 for Builds and Functions on October 1, 2026. How can I see which of my projects are affected? You can see which of your projects are affected by this deprecation with: Will my existing deployments be affected? No, existing deployments with Serverless Functions Invocations to already-deployed functions will continue to work normally. Only new deployments will be affected.will not be affected. When will I no long
-
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
-
- Pricing
-
Google Gemini 2.5 Pro removed from model options across all plans
-
- Models
-
Model microsoft/FrogBoss-32B-2510 with MIT license was removed from the available models.
-
- PricingLimitsDeprecationsModels
-
Feature naming and model offerings updated in Business and Enterprise plans (cosmetic/feature presentation changes, no price change)
-
Model upgrade paths for deprecated models changed to new gpt-5.6 series variants instead of gpt-5.4/5.5 series.
-
OpenAI API: 1 additive change
-
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.
-
- Models
-
Moonshot Kimi model K3 variant added with other license type and availability date of June 13, 2026.
-
-
-
Deprecation date: July 27, 2026 End of life date: November 23, 2026 The foundation_dns boolean is deprecated in the DNS settings endpoints for zone settings and account defaults. Use nameservers.type: "cloudflare.advanced" to configure Advanced Nameservers instead. Affected endpoints: /zones/{zone_id}/dns_settings /accounts/{account_id}/dns_settings Beginning October 26, 2026, the DNS settings API will gradually represent Advanced Nameservers with nameservers.type: "cloudflare.advanced". This ro
-
Enforcement date: September 27, 2026 Account names will be limited to a maximum of 65 characters across all account creation and update APIs. This limit applies to all accounts, including organization accounts. Currently, the account update API (PUT /accounts/{account_id}) already enforces this limit, while the account create API (POST /accounts) silently truncates names up to 120 bytes. This mismatch can result in accounts that are created successfully but cannot later be renamed. After Septemb
-
Deprecation date: July 21, 2026 The Account Roles API only returns account-level roles today, and is deprecated in favor of the Permission Groups API. The Permission Groups API is the supported way to enumerate account, zone, and resource-level roles that can be granted to account members. Deprecated APIs: GET /accounts/{account_id}/roles — List roles GET /accounts/{account_id}/roles/{role_id} — Role details Replacements: GET /accounts/{account_id}/iam/permission_groups — List account permission
-
Deprecation date: July 15, 2026 End of life date: October 15, 2026 The legacy Workers KV API routes under /accounts/{account_id}/workers/namespaces/* are deprecated in favor of the Workers KV API routes under /accounts/{account_id}/storage/kv/namespaces/*. The legacy and replacement routes are interchangeable. They accept the same request parameters and return the same response payloads. To migrate, update the URL path from /workers/namespaces/ to /storage/kv/namespaces/. Deprecated APIs: GET an
- Deprecation API deprecations - Zero Trust Networks Route Endpoints and Cloudflare Tunnel Connections Field 1mo ago
Deprecation date: July 9, 2026 End of life date: October 5, 2026 Two related changes to the Zero Trust Networks API and Cloudflare Tunnel API take effect on October 5, 2026. Route endpoints The CIDR-encoded route endpoints are deprecated in favor of the standard, route_id-based endpoints that already exist today. Deprecated APIs: POST /accounts/{account_id}/teamnet/routes/network/{ip_network_encoded} PATCH /accounts/{account_id}/teamnet/routes/network/{ip_network_encoded} DELETE /accounts/{accou
-
Deprecation date: September 18, 2025 End of life date: June 23, 2026 The AMP/SXG features have reached end of life. There will be no replacement functionality. The zone settings API endpoints and sxg Configuration Rule setting should no longer be used. Deprecated APIs: GET /zones/{zone_id}/amp/sxg PUT /zones/{zone_id}/amp/sxg Deprecated Configuration Rule setting: sxg The Dashboard UI will no longer show references to AMP or the sxg setting. Users can remove the sxg parameter from their rulesets
-
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 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 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 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
-
-
-
Specifying an explicit version in CREATE or ALTER EXTENSION is deprecated. From 2026-08-05 the version clause is ignored and the extension's default version is installed, with a warning. Starting 2026-08-05, specifying an explicit version when creating or updating a Postgres extension on Supabase is deprecated. Statements like: create extension pgvector version '0.7.0'; alter extension pg_graphql update to '1.5.9'; will still succeed, but the requested version is now ignored: the extension is in
-
What's Changing? The week of Aug 9, 2026, the default self-hosted Supabase API gateway will change from Kong to Envoy. Envoy has shipped as an optional override (docker-compose.envoy.yml) for the last several releases; it now becomes the default in docker-compose.yml, and Kong moves to an optional override. This is a breaking change for a subset of self-hosters (see below) - most notably anyone relying on Kong's built-in HTTPS listener, a customized kong.yml, or tooling that references the gatew
-
Deprecation notice: @supabase/supabase-js will require TypeScript 5.0 Summary Starting with a minor release on or after January 2027, @supabase/supabase-js and the packages it bundles (postgrest-js, auth-js, realtime-js, storage-js, functions-js) will require TypeScript 5.0 or later. TypeScript 4.7–4.9 will no longer be tested or supported. Consistent with our existing Support Policy, raising the minimum TypeScript version ships in a minor release and is not considered a breaking change, the sam
-
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) 3mo 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) 6mo 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
-
- Models
-
Two new IBM Granite 4.0 1B model variants added with Apache 2.0 license, available from 2025-10-07.
-
- Pricing
-
Pro plan upgraded from SWE 1.6 to SWE 1.7
-
- Models
-
License changed from 'other' to 'apache-2.0' for six OLMo model variants.
-
- Open AWS → current state & full history
- PricingOpen Bolt.new → current state & full history
- ModelsOpen Meta Llama → current state & full history
- ModelsOpen MiniMax → current state & full history
- ModelsOpen Zhipu GLM → current state & full history
No tools match these filters.