BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Breakwatch//API change radar//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:API deadlines (Breakwatch)
X-WR-CALDESC:Breaking changes and deprecation dates across the APIs on the 
 Breakwatch radar: https://www.breakwatch.ai/radar/calendar
REFRESH-INTERVAL;VALUE=DURATION:PT12H
X-PUBLISHED-TTL:PT12H
BEGIN:VEVENT
UID:openai-1790812805049-e00e8303@breakwatch.ai
DTSTAMP:20261001T000005Z
DTSTART;VALUE=DATE:20260826
DTEND;VALUE=DATE:20260827
SUMMARY:OpenAI shuts down the Assistants API on Aug 26\, 2026
DESCRIPTION:The Assistants API was permanently shut down on August 26\, 202
 6\, with no further access. Multiple transcription models (whisper-1\, gpt
 -4o-transcribe\, gpt-4o-mini-transcribe\, gpt-4o-transcribe-diarize) were 
 also announced as deprecated with a shutdown date of February 26\, 2027.\n
 \nWhat to do: Migrate from the Assistants API to the Responses API and Con
 versations API using the official migration guide immediately. For depreca
 ted transcription models\, migrate to gpt-live-transcribe or gpt-transcrib
 e before February 26\, 2027.\n\nDetails: https://www.breakwatch.ai/radar/o
 penai/changes/openai-shuts-down-assistants-api-aug-26-2026-1790812805049-e
 00e8303
URL:https://www.breakwatch.ai/radar/openai/changes/openai-shuts-down-assist
 ants-api-aug-26-2026-1790812805049-e00e8303
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: OpenAI shuts down the Assistants API on Aug 26\, 202
 6
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:hubspot-1787853604851-8f9f1613@breakwatch.ai
DTSTAMP:20260827T180004Z
DTSTART;VALUE=DATE:20260827
DTEND;VALUE=DATE:20260828
SUMMARY:HubSpot blocks new legacy private apps in the UI from Aug 27\, 2026
DESCRIPTION:HubSpot is permanently disabling the ability to create new lega
 cy\, non-Project-based private apps through the account UI\, announced Aug
 ust 27\, 2026. Users must migrate to Service Keys via Developer Platform P
 rojects version 2026.09.\n\nWhat to do: Stop creating legacy private apps 
 via the UI and migrate to Service Keys using Developer Platform Projects v
 ersion 2026.09.\n\nDetails: https://www.breakwatch.ai/radar/hubspot/change
 s/hubspot-blocks-legacy-private-apps-ui-aug-27-1787853604851-8f9f1613
URL:https://www.breakwatch.ai/radar/hubspot/changes/hubspot-blocks-legacy-p
 rivate-apps-ui-aug-27-1787853604851-8f9f1613
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: HubSpot blocks new legacy private apps in the UI fro
 m Aug 27\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-1787940002569-73f4cf4b@breakwatch.ai
DTSTAMP:20260828T180002Z
DTSTART;VALUE=DATE:20260828
DTEND;VALUE=DATE:20260829
SUMMARY:GitHub deprecates Classroom\, changes Copilot billing on Aug 28\, 2
 026
DESCRIPTION:Two new deprecation/retirement announcements were added: GitHub
  Classroom has been deprecated (community engagement)\, and upcoming chang
 es to GitHub Copilot policies and billing were announced. These join exist
 ing retirements already listed in the changelog.\n\nWhat to do: Review the
  GitHub Classroom deprecation notice and migrate any classroom integration
 s or workflows to alternatives. Also review the upcoming Copilot policy an
 d billing changes to assess impact on existing Copilot integrations and co
 st management.\n\nDetails: https://www.breakwatch.ai/radar/github/changes/
 github-deprecates-classroom-changes-copilot-billing-aug-28-1787940002569-7
 3f4cf4b
URL:https://www.breakwatch.ai/radar/github/changes/github-deprecates-classr
 oom-changes-copilot-billing-aug-28-1787940002569-73f4cf4b
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: GitHub deprecates Classroom\, changes Copilot billin
 g on Aug 28\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-1788480002055-18c3a556@breakwatch.ai
DTSTAMP:20260904T000002Z
DTSTART;VALUE=DATE:20260905
DTEND;VALUE=DATE:20260906
SUMMARY:GitHub CLI Linux package signing key expires on Sep 5\, 2026
DESCRIPTION:GitHub announced the upcoming deprecation of selected GitHub Co
 pilot models and the GitHub CLI Linux package signing key expires Septembe
 r 5\, 2026. Additionally\, new entries were added including Gemini 3.8 Fla
 sh availability and multiple trusted publishing configurations for npm.\n\
 nWhat to do: Rotate or update the GitHub CLI Linux package signing key bef
 ore September 5\, 2026 to avoid broken installs\; identify which Copilot m
 odels are being deprecated and migrate to supported alternatives.\n\nDetai
 ls: https://www.breakwatch.ai/radar/github/changes/github-cli-linux-packag
 e-signing-key-expires-sep-1788480002055-18c3a556
URL:https://www.breakwatch.ai/radar/github/changes/github-cli-linux-package
 -signing-key-expires-sep-1788480002055-18c3a556
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: GitHub CLI Linux package signing key expires on Sep 
 5\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:hubspot-1788868803368-55734966@breakwatch.ai
DTSTAMP:20260908T120003Z
DTSTART;VALUE=DATE:20260908
DTEND;VALUE=DATE:20260909
SUMMARY:HubSpot pipeline and stage deletes check references from Sep 8\, 20
 26
DESCRIPTION:HubSpot has added a new changelog entry announcing that Pipelin
 e and pipeline stage delete endpoints will validate references by default 
 starting with the 2026-09 API version (live September 8\, 2026). This is a
  breaking change affecting integrations that delete pipelines or pipeline 
 stages without first removing associated references.\n\nWhat to do: Review
  any integration logic that calls pipeline or pipeline stage delete endpoi
 nts and ensure all references (e.g.\, deals linked to pipeline stages) are
  removed or migrated before deletion\, prior to adopting the 2026-09 API v
 ersion.\n\nDetails: https://www.breakwatch.ai/radar/hubspot/changes/hubspo
 t-pipeline-stage-deletes-check-references-sep-8-1788868803368-55734966
URL:https://www.breakwatch.ai/radar/hubspot/changes/hubspot-pipeline-stage-
 deletes-check-references-sep-8-1788868803368-55734966
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: HubSpot pipeline and stage deletes check references 
 from Sep 8\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-1789063202227-2697937f@breakwatch.ai
DTSTAMP:20260910T180002Z
DTSTART;VALUE=DATE:20260910
DTEND;VALUE=DATE:20260911
SUMMARY:GitHub deprecates MAI-Code-1-Flash in Copilot on Sep 10\, 2026
DESCRIPTION:MAI-Code-1-Flash model has been deprecated in GitHub Copilot as
  of September 10\, 2026. Additionally\, a new Xcode 27 runner image on mac
 OS 27 and an npm security hold improvement were added.\n\nWhat to do: If y
 our Copilot integration or workflows reference the MAI-Code-1-Flash model 
 explicitly\, migrate to an alternative supported model. Review GitHub's Co
 pilot model documentation for recommended replacements.\n\nDetails: https:
 //www.breakwatch.ai/radar/github/changes/github-deprecates-mai-code-1-flas
 h-copilot-sep-1789063202227-2697937f
URL:https://www.breakwatch.ai/radar/github/changes/github-deprecates-mai-co
 de-1-flash-copilot-sep-1789063202227-2697937f
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: GitHub deprecates MAI-Code-1-Flash in Copilot on Sep
  10\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:twilio-1787767202673-7b13bc80@breakwatch.ai
DTSTAMP:20260826T180002Z
DTSTART;VALUE=DATE:20260913
DTEND;VALUE=DATE:20260914
SUMMARY:Twilio blocks new Functions Classic on Sep 13\, 2026 and auto-migra
 tes
DESCRIPTION:Twilio is deprecating Functions Classic\, with new creation blo
 cked from September 13\, 2026\, and automatic migration of all existing Fu
 nctions Classic to the new Functions platform between September 14 and Oct
 ober 26\, 2026. No customer action is required as Twilio will handle the m
 igration automatically.\n\nWhat to do: No action required for most custome
 rs — Twilio will auto-migrate existing Functions Classic\, URLs\, enviro
 nment variables\, and deployed code. Review the migration guide and consid
 er upgrading Node.js for the new Functions environment ahead of the Septem
 ber 13 cutoff.\n\nDetails: https://www.breakwatch.ai/radar/twilio/changes/
 twilio-blocks-functions-classic-sep-13-2026-auto-1787767202673-7b13bc80
URL:https://www.breakwatch.ai/radar/twilio/changes/twilio-blocks-functions-
 classic-sep-13-2026-auto-1787767202673-7b13bc80
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Twilio blocks new Functions Classic on Sep 13\, 2026
  and auto-migrates
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:twilio-1789689601992-5696bc35@breakwatch.ai
DTSTAMP:20260918T000001Z
DTSTART;VALUE=DATE:20260913
DTEND;VALUE=DATE:20260914
SUMMARY:Twilio ends Functions Classic Sep 13\, 2026\; Java SDK 13 fixes cra
 sh
DESCRIPTION:The Java Helper Library versions 10.0.0–12.1.1 have a latent 
 breaking bug where unknown fields in nested API responses cause a crash (A
 piConnectionException). Version 13.0.0 fixes this but itself introduces br
 eaking changes requiring a migration. Additionally\, Twilio Functions Clas
 sic is being deprecated and will be automatically migrated starting Septem
 ber 13\, 2026.\n\nWhat to do: Upgrade the Java Helper Library to 13.0.0 im
 mediately following the upgrade guide to avoid deserialization failures. F
 or Functions Classic\, review the migration guide before September 13\, 20
 26 when creation of new Classic Functions will be disabled.\n\nDetails: ht
 tps://www.breakwatch.ai/radar/twilio/changes/twilio-ends-functions-classic
 -sep-13-2026-java-1789689601992-5696bc35
URL:https://www.breakwatch.ai/radar/twilio/changes/twilio-ends-functions-cl
 assic-sep-13-2026-java-1789689601992-5696bc35
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Twilio ends Functions Classic Sep 13\, 2026\; Java S
 DK 13 fixes crash
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-1789495202039-24dc3edc@breakwatch.ai
DTSTAMP:20260915T180002Z
DTSTART;VALUE=DATE:20260915
DTEND;VALUE=DATE:20260916
SUMMARY:GitHub drops SHA-1 support for HTTPS connections on Sep 15\, 2026
DESCRIPTION:GitHub has sunset SHA-1 in HTTPS connections\, effective Septem
 ber 15\, 2026. This is a permanent removal with no fallback\, meaning clie
 nts relying on SHA-1 cipher suites for HTTPS communication with GitHub wil
 l be unable to connect.\n\nWhat to do: Ensure all HTTPS clients\, librarie
 s\, and tooling connecting to GitHub use SHA-2 (e.g.\, SHA-256) or stronge
 r cipher suites. Upgrade outdated TLS stacks or dependencies that rely on 
 SHA-1.\n\nDetails: https://www.breakwatch.ai/radar/github/changes/github-d
 rops-sha-1-support-https-connections-sep-1789495202039-24dc3edc
URL:https://www.breakwatch.ai/radar/github/changes/github-drops-sha-1-suppo
 rt-https-connections-sep-1789495202039-24dc3edc
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: GitHub drops SHA-1 support for HTTPS connections on 
 Sep 15\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:twilio-1789171202142-387cdfee@breakwatch.ai
DTSTAMP:20260912T000002Z
DTSTART;VALUE=DATE:20260915
DTEND;VALUE=DATE:20260916
SUMMARY:Twilio requires policy URLs on toll-free verifications Sep 15\, 202
 6
DESCRIPTION:Starting September 15\, 2026\, the privacy_policy_url and terms
 _and_conditions_url fields will become required on all new Toll-Free verif
 ication submissions\; submissions missing either field will be rejected. E
 xisting verified numbers are unaffected.\n\nWhat to do: Ensure all new Tol
 l-Free verification API calls include both privacy_policy_url and terms_an
 d_conditions_url fields before September 15\, 2026.\n\nDetails: https://ww
 w.breakwatch.ai/radar/twilio/changes/twilio-requires-policy-urls-toll-free
 -verifications-sep-1789171202142-387cdfee
URL:https://www.breakwatch.ai/radar/twilio/changes/twilio-requires-policy-u
 rls-toll-free-verifications-sep-1789171202142-387cdfee
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Twilio requires policy URLs on toll-free verificatio
 ns Sep 15\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:shopify-1794355204632-fc5300a2@breakwatch.ai
DTSTAMP:20261111T000004Z
DTSTART;VALUE=DATE:20260917
DTEND;VALUE=DATE:20260918
SUMMARY:Shopify removes session.currentSession.staffMemberId from POS UI Ex
 tensions in 2026-10
DESCRIPTION:Shopify removed session.currentSession.staffMemberId from POS U
 I Extensions in API version 2026-10. This field is no longer available and
  any extension relying on it will break.\n\nWhat to do: Audit any POS UI E
 xtensions that read session.currentSession.staffMemberId and migrate to an
  alternative source for staff member identification before upgrading to AP
 I version 2026-10.\n\nDetails: https://www.breakwatch.ai/radar/shopify/cha
 nges/shopify-removes-session-currentsession-staffmemberid-pos-ui-179435520
 4632-fc5300a2
URL:https://www.breakwatch.ai/radar/shopify/changes/shopify-removes-session
 -currentsession-staffmemberid-pos-ui-1794355204632-fc5300a2
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Shopify removes session.currentSession.staffMemberId
  from POS UI Extensions in 2026-10
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-1790078402361-c4a54a49@breakwatch.ai
DTSTAMP:20260922T120002Z
DTSTART;VALUE=DATE:20260922
DTEND;VALUE=DATE:20260923
SUMMARY:GitHub deprecates the all-platform CodeQL bundle on Sep 22\, 2026
DESCRIPTION:GitHub has issued a deprecation notice for the all-platform Cod
 eQL bundle\, announced on September 22\, 2026. This signals a future remov
 al of the bundled CodeQL distribution that targets all platforms.\n\nWhat 
 to do: Review your CodeQL workflows and CI pipelines that rely on the all-
 platform CodeQL bundle and plan to migrate to platform-specific CodeQL bun
 dles or alternative distribution methods before the sunset date.\n\nDetail
 s: https://www.breakwatch.ai/radar/github/changes/github-deprecates-all-pl
 atform-codeql-bundle-sep-22-1790078402361-c4a54a49
URL:https://www.breakwatch.ai/radar/github/changes/github-deprecates-all-pl
 atform-codeql-bundle-sep-22-1790078402361-c4a54a49
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: GitHub deprecates the all-platform CodeQL bundle on 
 Sep 22\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:shopify-1790100004391-274f0c68@breakwatch.ai
DTSTAMP:20260922T180004Z
DTSTART;VALUE=DATE:20260922
DTEND;VALUE=DATE:20260923
SUMMARY:Shopify cuts marketCurrencySettingsUpdate\, caps Events on Sep 22\,
  2026
DESCRIPTION:Two new breaking changes appeared in the diff: (1) Events subsc
 ription query complexity limit is changing to 100 points\, and (2) the mar
 ketCurrencySettingsUpdate mutation is being removed from the Admin GraphQL
  API. Both are tagged as breaking changes effective around September 22\, 
 2026.\n\nWhat to do: Remove or replace any usage of the marketCurrencySett
 ingsUpdate mutation before the 2026-10 API version\, and ensure Events sub
 scription queries stay within the new 100-point complexity limit.\n\nDetai
 ls: https://www.breakwatch.ai/radar/shopify/changes/shopify-cuts-marketcur
 rencysettingsupdate-caps-events-sep-22-1790100004391-274f0c68
URL:https://www.breakwatch.ai/radar/shopify/changes/shopify-cuts-marketcurr
 encysettingsupdate-caps-events-sep-22-1790100004391-274f0c68
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Shopify cuts marketCurrencySettingsUpdate\, caps Eve
 nts on Sep 22\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:shopify-1794484803990-98d11502@breakwatch.ai
DTSTAMP:20261112T120003Z
DTSTART;VALUE=DATE:20260922
DTEND;VALUE=DATE:20260923
SUMMARY:Shopify removes marketCurrencySettingsUpdate GraphQL mutation
DESCRIPTION:Shopify is removing the marketCurrencySettingsUpdate mutation f
 rom the GraphQL Admin API\, and two other features (Unlimited private plan
 s and a new translatable boolean Metafield field) have been removed from t
 he changelog. The mutation removal is a breaking change with no replacemen
 t mentioned.\n\nWhat to do: Audit any code using the marketCurrencySetting
 sUpdate mutation and migrate to an alternative approach for updating marke
 t currency settings before the removal takes effect around September 22\, 
 2026.\n\nDetails: https://www.breakwatch.ai/radar/shopify/changes/shopify-
 removes-marketcurrencysettingsupdate-graphql-1794484803990-98d11502
URL:https://www.breakwatch.ai/radar/shopify/changes/shopify-removes-marketc
 urrencysettingsupdate-graphql-1794484803990-98d11502
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Shopify removes marketCurrencySettingsUpdate GraphQL
  mutation
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-1790208002169-e53491c9@breakwatch.ai
DTSTAMP:20260924T000002Z
DTSTART;VALUE=DATE:20260923
DTEND;VALUE=DATE:20260924
SUMMARY:GitHub Actions drops Node 20 support on Sep 23\, 2026
DESCRIPTION:Node 20 is no longer available in GitHub Actions as of Septembe
 r 23\, 2026. Workflows relying on Node 20 runners or actions will break.\n
 \nWhat to do: Update GitHub Actions workflows and any custom actions to us
 e a supported Node.js version (e.g.\, Node 22). Check all node-version inp
 uts and action runtime declarations.\n\nDetails: https://www.breakwatch.ai
 /radar/github/changes/github-actions-drops-node-20-support-sep-23-17902080
 02169-e53491c9
URL:https://www.breakwatch.ai/radar/github/changes/github-actions-drops-nod
 e-20-support-sep-23-1790208002169-e53491c9
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: GitHub Actions drops Node 20 support on Sep 23\, 202
 6
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:supabase-1787551204978-86e319e5@breakwatch.ai
DTSTAMP:20260824T060004Z
DTSTART;VALUE=DATE:20260923
DTEND;VALUE=DATE:20260924
SUMMARY:Supabase removes the logs.all Management API endpoint on Sep 23\, 2
 026
DESCRIPTION:The Supabase Management API logs.all analytics endpoint is bein
 g removed on 2026-09-23 and must be replaced with the new ClickHouse-backe
 d logs endpoint\, which only accepts ClickHouse SQL. Multiple other breaki
 ng changes are also present including Envoy replacing Kong as default API 
 gateway\, realtime schema lockdown\, OAuth token endpoint returning HTTP 2
 00 instead of 201\, and several self-hosted configuration changes.\n\nWhat
  to do: Migrate scripts from logs.all to the new logs endpoint using Click
 House SQL before 2026-09-23. Additionally: update OAuth token checks from 
 status 201 to any 2XX\; if self-hosted\, prepare for Envoy replacing Kong 
 (week of 2026-08-09) and opt back into Kong if needed\; note that extensio
 n version pinning in CREATE/ALTER EXTENSION is ignored from 2026-08-05\; a
 nd review all other breaking changes for their respective effective dates.
 \n\nDetails: https://www.breakwatch.ai/radar/supabase/changes/supabase-rem
 oves-logs-all-management-api-endpoint-sep-1787551204978-86e319e5
URL:https://www.breakwatch.ai/radar/supabase/changes/supabase-removes-logs-
 all-management-api-endpoint-sep-1787551204978-86e319e5
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Supabase removes the logs.all Management API endpoin
 t on Sep 23\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:supabase-1790575204689-c63b0be3@breakwatch.ai
DTSTAMP:20260928T060004Z
DTSTART;VALUE=DATE:20260928
DTEND;VALUE=DATE:20260929
SUMMARY:Supabase ships breaking Postgres 15.19/17.11 updates on Sep 28\, 20
 26
DESCRIPTION:Supabase is rolling out PostgreSQL 15.19/17.11 minor releases t
 hat include four potentially breaking changes: ltree indexes may need rein
 dexing\, pgcrypto stops decrypting legacy-cipher (Blowfish/CAST5) PGP data
  by default\, btree_gist indexes on float columns containing NaN need rein
 dexing\, and custom operators with non-built-in selectivity estimators now
  require superuser to recreate.\n\nWhat to do: Run the provided detection 
 queries for each affected area. Reindex affected ltree and btree_gist inde
 xes using REINDEX INDEX CONCURRENTLY. Re-encrypt pgcrypto data using ciphe
 r-algo=aes256. Recreate custom operators without RESTRICT/JOIN clauses or 
 switch to built-in estimators. Upgrade available in dashboard from 2026-09
 -28.\n\nDetails: https://www.breakwatch.ai/radar/supabase/changes/supabase
 -ships-breaking-postgres-15-19-17-11-1790575204689-c63b0be3
URL:https://www.breakwatch.ai/radar/supabase/changes/supabase-ships-breakin
 g-postgres-15-19-17-11-1790575204689-c63b0be3
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Supabase ships breaking Postgres 15.19/17.11 updates
  on Sep 28\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:stripe-1790877602935-3fcb2181@breakwatch.ai
DTSTAMP:20261001T180002Z
DTSTART;VALUE=DATE:20260930
DTEND;VALUE=DATE:20261001
SUMMARY:Stripe drops payment_method_types in Endive API version on Sep 30\,
  2026
DESCRIPTION:Stripe's upcoming 'Endive' API version (2026-09-30) introduces 
 numerous breaking changes including removal of payment_method_types parame
 ter from Checkout Sessions\, Payment Intents\, and Setup Intents\, removal
  of PayTo-specific fields from Payment Methods\, removal of payment_method
 _types option in Elements\, and several other incompatible changes across 
 Payments\, Connect\, Billing\, and Financial Connections surfaces.\n\nWhat
  to do: Review the full Endive changelog at https://stripe.com/docs/upgrad
 es and audit all usages of payment_method_types in Checkout Sessions\, Pay
 ment Intents\, Setup Intents\, and Elements before migrating to API versio
 n 2026-09-30. Also check for PayTo-specific Payment Method fields and Fina
 ncial Connections countries filter usages.\n\nDetails: https://www.breakwa
 tch.ai/radar/stripe/changes/stripe-drops-payment-method-types-endive-api-v
 ersion-1790877602935-3fcb2181
URL:https://www.breakwatch.ai/radar/stripe/changes/stripe-drops-payment-met
 hod-types-endive-api-version-1790877602935-3fcb2181
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Stripe drops payment_method_types in Endive API vers
 ion on Sep 30\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:twilio-1790359202888-463af008@breakwatch.ai
DTSTAMP:20260925T180002Z
DTSTART;VALUE=DATE:20260930
DTEND;VALUE=DATE:20261001
SUMMARY:Twilio Conferences list defaults to in-progress only on Sep 30\, 20
 26
DESCRIPTION:Starting September 30\, 2026\, the Voice API Conference list en
 dpoint (GET /2010-04-01/Accounts/{AccountSid}/Conferences.json) will chang
 e its default behavior to return only in-progress conferences instead of a
 ll conferences. Additionally\, the Verify Event Streams 'Attempt DLR' even
 t type will be discontinued after September 22\, 2026.\n\nWhat to do: For 
 the Conference list endpoint\, explicitly pass a Status filter parameter i
 f you need conferences in states other than 'in-progress'. For Verify Even
 t Streams\, remove any subscriptions to the 'Attempt DLR' event type and m
 igrate to alternative event types before September 22\, 2026.\n\nDetails: 
 https://www.breakwatch.ai/radar/twilio/changes/twilio-conferences-list-def
 aults-progress-only-sep-30-1790359202888-463af008
URL:https://www.breakwatch.ai/radar/twilio/changes/twilio-conferences-list-
 defaults-progress-only-sep-30-1790359202888-463af008
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Twilio Conferences list defaults to in-progress only
  on Sep 30\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:shopify-1789668003971-12bc297a@breakwatch.ai
DTSTAMP:20260917T180003Z
DTSTART;VALUE=DATE:20261001
DTEND;VALUE=DATE:20261002
SUMMARY:Shopify removes staffMemberId from POS UI Extensions on Oct 1\, 202
 6
DESCRIPTION:Three new breaking/action-required changes appeared in the diff
 : (1) session.currentSession.staffMemberId removed from POS UI Extensions 
 in 2026-10\, (2) a canceled receive action added to the inventory shipment
 s API\, and (3) new Pricing audit trail for contextual product variant pri
 ces. The most impactful is the removal of staffMemberId from POS UI Extens
 ions\, which is a hard breaking change in the 2026-10 API version.\n\nWhat
  to do: Remove references to session.currentSession.staffMemberId in POS U
 I Extensions before upgrading to API version 2026-10. Review the inventory
  shipments API and pricing audit trail additions for integration opportuni
 ties.\n\nDetails: https://www.breakwatch.ai/radar/shopify/changes/shopify-
 removes-staffmemberid-pos-ui-extensions-oct-1-1789668003971-12bc297a
URL:https://www.breakwatch.ai/radar/shopify/changes/shopify-removes-staffme
 mberid-pos-ui-extensions-oct-1-1789668003971-12bc297a
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Shopify removes staffMemberId from POS UI Extensions
  on Oct 1\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-1790791202258-fe39910f@breakwatch.ai
DTSTAMP:20260930T180002Z
DTSTART;VALUE=DATE:20261007
DTEND;VALUE=DATE:20261008
SUMMARY:GitHub drops X25519-only TLS support for GHE.com on Oct 7\, 2026
DESCRIPTION:GitHub has retired X25519-only TLS support for GHE.com\, effect
 ive October 7. This means clients that only support X25519 key exchange fo
 r TLS connections to GHE.com will stop working after that date.\n\nWhat to
  do: Ensure your TLS clients and libraries support additional key exchange
  algorithms beyond X25519 (e.g.\, ECDHE with P-256) before October 7 to av
 oid connection failures to GHE.com.\n\nDetails: https://www.breakwatch.ai/
 radar/github/changes/github-drops-x25519-only-tls-support-ghe-com-17907912
 02258-fe39910f
URL:https://www.breakwatch.ai/radar/github/changes/github-drops-x25519-only
 -tls-support-ghe-com-1790791202258-fe39910f
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: GitHub drops X25519-only TLS support for GHE.com on 
 Oct 7\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:shopify-1791417603780-a83b9dc7@breakwatch.ai
DTSTAMP:20261008T000003Z
DTSTART;VALUE=DATE:20261007
DTEND;VALUE=DATE:20261008
SUMMARY:Shopify POS UI extensions return percent discount values Oct 7\, 20
 26
DESCRIPTION:POS UI extensions in API version 2026-10 now return percentage 
 values for percentage discounts\, which is a breaking change in how discou
 nt values are represented. This is a newly added changelog entry not prese
 nt in the previous diff.\n\nWhat to do: Update your POS UI extension code 
 that reads discount values to handle percentage discounts as percentage va
 lues rather than the previous format. Review the 2026-10 release notes for
  exact payload structure changes.\n\nDetails: https://www.breakwatch.ai/ra
 dar/shopify/changes/shopify-pos-ui-extensions-return-percent-discount-valu
 es-1791417603780-a83b9dc7
URL:https://www.breakwatch.ai/radar/shopify/changes/shopify-pos-ui-extensio
 ns-return-percent-discount-values-1791417603780-a83b9dc7
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Shopify POS UI extensions return percent discount va
 lues Oct 7\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-1792087202505-b028493d@breakwatch.ai
DTSTAMP:20261015T180002Z
DTSTART;VALUE=DATE:20261015
DTEND;VALUE=DATE:20261016
SUMMARY:GitHub retires email notifications for repository pushes on Oct 15\
 , 2026
DESCRIPTION:Email notifications for repository push events have been retire
 d as of October 15\, 2026. Users and integrations relying on these notific
 ations will no longer receive them.\n\nWhat to do: Review any workflows or
  integrations that depend on email notifications for repository push event
 s and migrate to alternative notification mechanisms such as webhooks or G
 itHub Actions.\n\nDetails: https://www.breakwatch.ai/radar/github/changes/
 github-retires-email-notifications-repository-pushes-oct-15-1792087202505-
 b028493d
URL:https://www.breakwatch.ai/radar/github/changes/github-retires-email-not
 ifications-repository-pushes-oct-15-1792087202505-b028493d
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: GitHub retires email notifications for repository pu
 shes on Oct 15\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-1792411201999-9d0213a6@breakwatch.ai
DTSTAMP:20261019T120002Z
DTSTART;VALUE=DATE:20261019
DTEND;VALUE=DATE:20261020
SUMMARY:GitHub alters CodeQL for macOS 27\, Xcode 27\, Swift 6.4 on Oct 19\
 , 2026
DESCRIPTION:GitHub added a new 'Retired' changelog entry on Oct 19 announci
 ng CodeQL changes for macOS 27\, Xcode 27\, and Swift 6.4\, indicating dep
 recation or breaking changes to CodeQL support for those platforms. This i
 s the only meaningful diff between the two versions.\n\nWhat to do: Review
  the 'CodeQL changes for macOS 27\, Xcode 27\, and Swift 6.4' changelog en
 try and update your CodeQL workflows and runner configurations to accommod
 ate the new requirements or removed support.\n\nDetails: https://www.break
 watch.ai/radar/github/changes/github-alters-codeql-macos-27-xcode-27-swift
 -1792411201999-9d0213a6
URL:https://www.breakwatch.ai/radar/github/changes/github-alters-codeql-mac
 os-27-xcode-27-swift-1792411201999-9d0213a6
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: GitHub alters CodeQL for macOS 27\, Xcode 27\, Swift
  6.4 on Oct 19\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-1792454402499-6d7f9cfa@breakwatch.ai
DTSTAMP:20261020T000002Z
DTSTART;VALUE=DATE:20261019
DTEND;VALUE=DATE:20261020
SUMMARY:GitHub removes deprecated Copilot models on Oct 19\, 2026
DESCRIPTION:GitHub Copilot models were deprecated and removed on October 19
 \, 2026\, and a new Copilot model policy API has been introduced for enter
 prise\, organizations\, and teams. Integrations relying on the deprecated 
 models will break immediately.\n\nWhat to do: Audit your Copilot API integ
 rations for deprecated model references and migrate to supported models. U
 se the new Copilot model policy API to manage allowed models at the enterp
 rise/org/team level.\n\nDetails: https://www.breakwatch.ai/radar/github/ch
 anges/github-removes-deprecated-copilot-models-oct-19-2026-1792454402499-6
 d7f9cfa
URL:https://www.breakwatch.ai/radar/github/changes/github-removes-deprecate
 d-copilot-models-oct-19-2026-1792454402499-6d7f9cfa
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: GitHub removes deprecated Copilot models on Oct 19\,
  2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:shopify-1793232004010-db9355a3@breakwatch.ai
DTSTAMP:20261029T000004Z
DTSTART;VALUE=DATE:20261028
DTEND;VALUE=DATE:20261029
SUMMARY:Shopify Admin REST API breaking change for Managed mode for Shopify
  Tax in October 2026
DESCRIPTION:Shopify introduced a breaking change in the Admin REST API rela
 ted to Managed mode for Shopify Tax\, announced on October 28\, 2026. Addi
 tionally\, first sign-ins to customer accounts now trigger Customer.state 
 changes and customers/enable webhooks in the GraphQL Admin API.\n\nWhat to
  do: Review the Shopify Tax Managed mode breaking change in the Admin REST
  API and update integrations accordingly. Also verify handling of Customer
 .state and customers/enable webhooks for first-time customer account sign-
 ins.\n\nDetails: https://www.breakwatch.ai/radar/shopify/changes/shopify-a
 dmin-rest-api-breaking-change-managed-mode-1793232004010-db9355a3
URL:https://www.breakwatch.ai/radar/shopify/changes/shopify-admin-rest-api-
 breaking-change-managed-mode-1793232004010-db9355a3
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Shopify Admin REST API breaking change for Managed m
 ode for Shopify Tax in October 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:shopify-1791590403400-81d6f3da@breakwatch.ai
DTSTAMP:20261010T000003Z
DTSTART;VALUE=DATE:20261102
DTEND;VALUE=DATE:20261103
SUMMARY:Shopify shuts down the Global Catalog REST API on Nov 2\, 2026
DESCRIPTION:The Global Catalog REST API will stop serving traffic on Novemb
 er 2\, 2026\, as announced on October 9. This is a hard end-of-life date f
 or the REST endpoint.\n\nWhat to do: Migrate from the Global Catalog REST 
 API to the Catalog GraphQL API before November 2\, 2026 to avoid service d
 isruption.\n\nDetails: https://www.breakwatch.ai/radar/shopify/changes/sho
 pify-shuts-down-global-catalog-rest-api-nov-1791590403400-81d6f3da
URL:https://www.breakwatch.ai/radar/shopify/changes/shopify-shuts-down-glob
 al-catalog-rest-api-nov-1791590403400-81d6f3da
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Shopify shuts down the Global Catalog REST API on No
 v 2\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:supabase-1793815205009-6bee6b34@breakwatch.ai
DTSTAMP:20261104T180005Z
DTSTART;VALUE=DATE:20261102
DTEND;VALUE=DATE:20261103
SUMMARY:Supabase CLI v3 defaults to local\, requires --remote on Nov 2\, 20
 26
DESCRIPTION:Supabase CLI v3.0.0 changes default command targets (local inst
 ead of hosted)\, requires explicit --remote and --yes flags for hosted/una
 ttended operations\, removes deprecated commands and config keys\, and is 
 now installed by default via npm\, Homebrew\, Scoop\, and setup-cli. Pipel
 ines and CI scripts that install the latest CLI without pinning a version 
 are immediately affected.\n\nWhat to do: Add --remote to any command targe
 ting a hosted project\, add --yes to unattended hosted changes in CI\, ren
 ame [inbucket] to [local_smtp] in config.toml\, and pin v2 (npm install su
 pabase@v2.stable) if not ready to migrate.\n\nDetails: https://www.breakwa
 tch.ai/radar/supabase/changes/supabase-cli-v3-defaults-local-requires-remo
 te-nov-1793815205009-6bee6b34
URL:https://www.breakwatch.ai/radar/supabase/changes/supabase-cli-v3-defaul
 ts-local-requires-remote-nov-1793815205009-6bee6b34
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Supabase CLI v3 defaults to local\, requires --remot
 e on Nov 2\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:hubspot-1793772003800-812a29c4@breakwatch.ai
DTSTAMP:20261104T060003Z
DTSTART;VALUE=DATE:20261103
DTEND;VALUE=DATE:20261104
SUMMARY:HubSpot sunsets design manager serverless functions and Node.js ≤
 20 runtimes on Nov 3\, 2026
DESCRIPTION:HubSpot is sunsetting design manager serverless functions and N
 ode.js 20 and earlier runtimes for workflow custom code actions\, effectiv
 e November 3\, 2026. These runtimes no longer receive security updates.\n\
 nWhat to do: Migrate serverless functions out of the design manager and up
 grade workflow custom code actions to Node.js 22 or later before November 
 3\, 2026.\n\nDetails: https://www.breakwatch.ai/radar/hubspot/changes/hubs
 pot-sunsets-design-manager-serverless-functions-node-js-1793772003800-812a
 29c4
URL:https://www.breakwatch.ai/radar/hubspot/changes/hubspot-sunsets-design-
 manager-serverless-functions-node-js-1793772003800-812a29c4
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: HubSpot sunsets design manager serverless functions 
 and Node.js ≤20 runtimes on Nov 3\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:slack-1794268804164-d18fb3a1@breakwatch.ai
DTSTAMP:20261110T000004Z
DTSTART;VALUE=DATE:20261106
DTEND;VALUE=DATE:20261107
SUMMARY:Slack Work Objects embeds require slack-mcps.com frame ancestor fro
 m November 6\, 2026
DESCRIPTION:Slack Work Objects embeds now require https://*.slack-mcps.com 
 in the Content-Security-Policy frame-ancestors directive. Embeds will fail
  to load if any of the three required origins is missing from the CSP head
 er.\n\nWhat to do: Update your Content-Security-Policy header to include a
 ll three required frame-ancestors origins: https://*.slack.com https://*.s
 lack-gov.com https://*.slack-mcps.com\n\nDetails: https://www.breakwatch.a
 i/radar/slack/changes/slack-work-objects-embeds-require-slack-mcps-com-179
 4268804164-d18fb3a1
URL:https://www.breakwatch.ai/radar/slack/changes/slack-work-objects-embeds
 -require-slack-mcps-com-1794268804164-d18fb3a1
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Slack Work Objects embeds require slack-mcps.com fra
 me ancestor from November 6\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:supabase-1791979203670-e9e842e9@breakwatch.ai
DTSTAMP:20261014T120003Z
DTSTART;VALUE=DATE:20261110
DTEND;VALUE=DATE:20261111
SUMMARY:Supabase drops CBC TLS 1.2 cipher suites from its APIs on Nov 10\, 
 2026
DESCRIPTION:Supabase will remove four CBC-mode TLS 1.2 cipher suites (TLS_E
 CDHE_*_WITH_AES_*_CBC_SHA*) from all project HTTP APIs (Auth\, Data API\, 
 Storage\, Realtime\, Edge Functions) starting November 10\, 2026. Clients 
 using only these deprecated ciphers will lose connectivity.\n\nWhat to do:
  Verify that all clients connecting to Supabase over HTTPS support at leas
 t one GCM or ChaCha20-Poly1305 TLS 1.2 cipher or TLS 1.3. Update end-of-li
 fe OS or TLS libraries accordingly before November 10\, 2026.\n\nDetails: 
 https://www.breakwatch.ai/radar/supabase/changes/supabase-drops-cbc-tls-1-
 2-cipher-suites-1791979203670-e9e842e9
URL:https://www.breakwatch.ai/radar/supabase/changes/supabase-drops-cbc-tls
 -1-2-cipher-suites-1791979203670-e9e842e9
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Supabase drops CBC TLS 1.2 cipher suites from its AP
 Is on Nov 10\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:supabase-1794031205237-032a5be1@breakwatch.ai
DTSTAMP:20261107T060005Z
DTSTART;VALUE=DATE:20261111
DTEND;VALUE=DATE:20261112
SUMMARY:supabase-flutter v3 breaks Dart/Flutter API surface with stable rel
 ease on Nov 11\, 2026
DESCRIPTION:supabase-flutter v3 introduces sweeping breaking changes to the
  Flutter/Dart client library\, including renamed packages\, changed API si
 gnatures\, new type system\, and altered defaults (e.g. order() sort direc
 tion). Stable release is planned for November 11\, 2026\, with v2 receivin
 g security fixes for 6 months afterward.\n\nWhat to do: Before upgrading: 
 add ascending: false to all order() calls relying on descending order whil
 e still on v2. Then bump to ^3.0.0\, replace renamed packages (gotrue→su
 pabase_auth\, realtime_client→supabase_realtime\, etc.)\, fix compile er
 rors per the migration guide\, and coordinate simultaneous release of apps
  sharing realtime broadcast channels.\n\nDetails: https://www.breakwatch.a
 i/radar/supabase/changes/supabase-flutter-v3-breaks-dart-flutter-api-surfa
 ce-1794031205237-032a5be1
URL:https://www.breakwatch.ai/radar/supabase/changes/supabase-flutter-v3-br
 eaks-dart-flutter-api-surface-1794031205237-032a5be1
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: supabase-flutter v3 breaks Dart/Flutter API surface 
 with stable release on Nov 11\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:shopify-1794614405083-4c5edf95@breakwatch.ai
DTSTAMP:20261114T000005Z
DTSTART;VALUE=DATE:20261113
DTEND;VALUE=DATE:20261114
SUMMARY:Shopify Storefront API 2027-01 makes Market.metafields key matching
  case-insensitive
DESCRIPTION:Shopify Storefront API 2027-01 introduces a breaking change whe
 re Market.metafields now matches keys in any case (case-insensitive). Addi
 tionally\, market metafields break ties between equally specific markets b
 y market handle\, and Checkout Function cart.deliverableLine inputs now mo
 del cost and link to their relevant cart.line.\n\nWhat to do: Audit any co
 de relying on case-sensitive metafield key matching in Market.metafields q
 ueries against Storefront API 2027-01+. Also review market tie-breaking lo
 gic and Checkout Function cart.deliverableLine usage for cost and line lin
 kage changes.\n\nDetails: https://www.breakwatch.ai/radar/shopify/changes/
 shopify-storefront-api-2027-01-makes-market-metafields-1794614405083-4c5ed
 f95
URL:https://www.breakwatch.ai/radar/shopify/changes/shopify-storefront-api-
 2027-01-makes-market-metafields-1794614405083-4c5edf95
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Shopify Storefront API 2027-01 makes Market.metafiel
 ds key matching case-insensitive
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:discord-1786752006825-4b8a6893@breakwatch.ai
DTSTAMP:20260815T000006Z
DTSTART;VALUE=DATE:20261116
DTEND;VALUE=DATE:20261117
SUMMARY:Discord stops listing channels bots cannot view in GET guild channe
 ls on Nov 16\, 2026
DESCRIPTION:Discord is changing channel visibility for bots: over the Gatew
 ay\, channels a bot lacks VIEW_CHANNEL on will have sensitive fields obfus
 cated (name becomes '___hidden___'\, new CHANNEL_OBFUSCATED flag set)\, an
 d over HTTP\, GET /guilds/{guild.id}/channels will omit inaccessible chann
 els entirely starting November 16\, 2026. Additionally\, the channel objec
 t's application_id field is now nullable\, which is a minor breaking chang
 e for code assuming it is always a snowflake when present.\n\nWhat to do: 
 Audit any bot logic that reads channels it may not have VIEW_CHANNEL permi
 ssion for (e.g.\, full channel list mirroring\, permission auditing\, chan
 nel structure reporting). Use the CHANNEL_OBFUSCATED flag (1 << 17) to det
 ect obfuscated channels. Test Gateway behavior now by sending capability 1
  << 15 in the Identify payload or enabling the 'Private Channel Obfuscatio
 n' toggle in the Developer Portal. Update code to handle application_id as
  nullable on channel objects.\n\nDetails: https://www.breakwatch.ai/radar/
 discord/changes/discord-stops-listing-channels-bots-cannot-view-get-178675
 2006825-4b8a6893
URL:https://www.breakwatch.ai/radar/discord/changes/discord-stops-listing-c
 hannels-bots-cannot-view-get-1786752006825-4b8a6893
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Discord stops listing channels bots cannot view in G
 ET guild channels on Nov 16\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-1792108802234-3bd6a110@breakwatch.ai
DTSTAMP:20261016T000002Z
DTSTART;VALUE=DATE:20261116
DTEND;VALUE=DATE:20261117
SUMMARY:GitHub retires selected Copilot models on Nov 16\, 2026
DESCRIPTION:GitHub has announced the upcoming deprecation of selected GitHu
 b Copilot models in mid-November 2026. This is a forward-looking retiremen
 t notice giving developers roughly a month to migrate to supported models.
 \n\nWhat to do: Identify which Copilot models you are currently using and 
 migrate to non-deprecated alternatives before mid-November 2026. Check the
  linked changelog entry for the specific model list.\n\nDetails: https://w
 ww.breakwatch.ai/radar/github/changes/github-retires-selected-copilot-mode
 ls-nov-16-2026-1792108802234-3bd6a110
URL:https://www.breakwatch.ai/radar/github/changes/github-retires-selected-
 copilot-models-nov-16-2026-1792108802234-3bd6a110
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: GitHub retires selected Copilot models on Nov 16\, 2
 026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:shopify-1793923204621-b36482fc@breakwatch.ai
DTSTAMP:20261106T000004Z
DTSTART;VALUE=DATE:20261120
DTEND;VALUE=DATE:20261121
SUMMARY:Shopify requires IP allowlist for all public apps by Nov 20\, 2026
DESCRIPTION:Shopify now requires an IP allowlist for every public app by No
 vember 20\, 2026 (or November 11 for apps using bulk operations). ASN supp
 ort is available for serverless hosting providers.\n\nWhat to do: Configur
 e an IP allowlist for your public app before November 20\, 2026 (or Novemb
 er 11 if your app uses bulk operations). If you use serverless hosting\, l
 everage the new ASN-based allowlist support in the Dev Dashboard.\n\nDetai
 ls: https://www.breakwatch.ai/radar/shopify/changes/shopify-requires-ip-al
 lowlist-all-public-apps-nov-1793923204621-b36482fc
URL:https://www.breakwatch.ai/radar/shopify/changes/shopify-requires-ip-all
 owlist-all-public-apps-nov-1793923204621-b36482fc
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Shopify requires IP allowlist for all public apps by
  Nov 20\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-1794657602733-362a6911@breakwatch.ai
DTSTAMP:20261114T120002Z
DTSTART;VALUE=DATE:20261201
DTEND;VALUE=DATE:20261202
SUMMARY:GitHub deprecates selected Copilot models in December 2026
DESCRIPTION:GitHub has announced the upcoming deprecation of selected GitHu
 b Copilot models in December 2026. This affects developers relying on spec
 ific Copilot models via the API.\n\nWhat to do: Identify which Copilot mod
 els your integration uses and migrate to supported alternatives before Dec
 ember 2026. Monitor GitHub's Copilot model documentation for the specific 
 list of deprecated models.\n\nDetails: https://www.breakwatch.ai/radar/git
 hub/changes/github-deprecates-selected-copilot-models-december-2026-179465
 7602733-362a6911
URL:https://www.breakwatch.ai/radar/github/changes/github-deprecates-select
 ed-copilot-models-december-2026-1794657602733-362a6911
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: GitHub deprecates selected Copilot models in Decembe
 r 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:supabase-1791309605920-4948352b@breakwatch.ai
DTSTAMP:20261006T180005Z
DTSTART;VALUE=DATE:20261201
DTEND;VALUE=DATE:20261202
SUMMARY:Supabase removes @supabase/server framework adapters on Dec 1\, 202
 6
DESCRIPTION:The four framework adapters in @supabase/server (/adapters/hono
 \, /adapters/h3\, /adapters/elysia\, /adapters/nestjs) are deprecated and 
 will be removed on December 1\, 2026. Developers must migrate to a framewo
 rk-specific bridge file that wraps @supabase/middleware entries.\n\nWhat t
 o do: Copy the appropriate bridge file for your framework (Hono\, H3\, Ely
 sia\, NestJS\, or TanStack Start) from the Supabase frameworks guide into 
 your project. Add @supabase/middleware as a direct dependency\, replace ad
 apter registrations with bridge calls (e.g.\, toHono([withRequiredClaims()
 \, withSupabaseClient()]))\, and update call sites from nested supabaseCon
 text to flat keys like c.var.supabase and c.var.jwtClaims.\n\nDetails: htt
 ps://www.breakwatch.ai/radar/supabase/changes/supabase-removes-supabase-se
 rver-framework-adapters-dec-1-1791309605920-4948352b
URL:https://www.breakwatch.ai/radar/supabase/changes/supabase-removes-supab
 ase-server-framework-adapters-dec-1-1791309605920-4948352b
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Supabase removes @supabase/server framework adapters
  on Dec 1\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-1793664002313-e97239e5@breakwatch.ai
DTSTAMP:20261103T000002Z
DTSTART;VALUE=DATE:20261202
DTEND;VALUE=DATE:20261203
SUMMARY:GitHub blocks pull_request_target by default in Actions on Dec 2\, 
 2026
DESCRIPTION:GitHub Actions will block the pull_request_target event by defa
 ult starting December 2\, 2026. This is a security-driven behavioral chang
 e that will affect workflows currently relying on this trigger without exp
 licit opt-in.\n\nWhat to do: Audit all workflows using pull_request_target
  and explicitly configure them to opt in or migrate to safer alternatives 
 before December 2\, 2026.\n\nDetails: https://www.breakwatch.ai/radar/gith
 ub/changes/github-blocks-pull-request-target-default-actions-dec-179366400
 2313-e97239e5
URL:https://www.breakwatch.ai/radar/github/changes/github-blocks-pull-reque
 st-target-default-actions-dec-1793664002313-e97239e5
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: GitHub blocks pull_request_target by default in Acti
 ons on Dec 2\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:hubspot-1786730404230-08339237@breakwatch.ai
DTSTAMP:20260814T180004Z
DTSTART;VALUE=DATE:20261204
DTEND;VALUE=DATE:20261205
SUMMARY:HubSpot retires Pipelines API v1 on Dec 4\, 2026
DESCRIPTION:HubSpot has announced the sunset of Pipelines API V1 on Decembe
 r 4\, 2026. After this date\, V1 endpoints will no longer be supported and
  integrations must migrate to the 2026-03 or later API version.\n\nWhat to
  do: Migrate all Pipelines API V1 endpoint calls to the 2026-03 (or newer)
  versioned endpoints before December 4\, 2026.\n\nDetails: https://www.bre
 akwatch.ai/radar/hubspot/changes/hubspot-retires-pipelines-api-v1-dec-4-20
 26-1786730404230-08339237
URL:https://www.breakwatch.ai/radar/hubspot/changes/hubspot-retires-pipelin
 es-api-v1-dec-4-2026-1786730404230-08339237
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: HubSpot retires Pipelines API v1 on Dec 4\, 2026
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:shopify-1789776003531-3a2d0847@breakwatch.ai
DTSTAMP:20260919T000003Z
DTSTART;VALUE=DATE:20270101
DTEND;VALUE=DATE:20270102
SUMMARY:Shopify removes automaticDiscounts query in Admin GraphQL API 2027-
 01
DESCRIPTION:The automaticDiscounts query is being removed in Admin GraphQL 
 API version 2027-01. This is a breaking change announced on September 18\,
  2026.\n\nWhat to do: Audit any usage of the automaticDiscounts query and 
 migrate to the replacement API before upgrading to API version 2027-01.\n\
 nDetails: https://www.breakwatch.ai/radar/shopify/changes/shopify-removes-
 automaticdiscounts-query-admin-graphql-api-1789776003531-3a2d0847
URL:https://www.breakwatch.ai/radar/shopify/changes/shopify-removes-automat
 icdiscounts-query-admin-graphql-api-1789776003531-3a2d0847
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Shopify removes automaticDiscounts query in Admin Gr
 aphQL API 2027-01
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:shopify-1793167204337-9a40c434@breakwatch.ai
DTSTAMP:20261028T060004Z
DTSTART;VALUE=DATE:20270101
DTEND;VALUE=DATE:20270102
SUMMARY:Shopify requires migration to expiring offline access tokens by Jan
  1\, 2027
DESCRIPTION:Shopify is requiring all apps to migrate to expiring offline ac
 cess tokens before January 1\, 2027. This is an action-required breaking c
 hange with a firm deadline\, accompanied by new security features includin
 g network access rules\, IP allowlists\, and client credentials access.\n\
 nWhat to do: Migrate your app to use expiring offline access tokens before
  January 1\, 2027. Review the new network access rules in shopify.app.toml
  and consider setting up an IP allowlist for Admin API access via the Dev 
 Dashboard.\n\nDetails: https://www.breakwatch.ai/radar/shopify/changes/sho
 pify-requires-migration-expiring-offline-access-tokens-1793167204337-9a40c
 434
URL:https://www.breakwatch.ai/radar/shopify/changes/shopify-requires-migrat
 ion-expiring-offline-access-tokens-1793167204337-9a40c434
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Shopify requires migration to expiring offline acces
 s tokens by Jan 1\, 2027
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:shopify-1793685603902-731fc2b3@breakwatch.ai
DTSTAMP:20261103T060003Z
DTSTART;VALUE=DATE:20270101
DTEND;VALUE=DATE:20270102
SUMMARY:Shopify breaks currententrychange event and makes Gift Card line_it
 em_id read-only in 2027-01
DESCRIPTION:Shopify added two breaking change announcements: the Customer A
 ccount API's currententrychange event will now return the previous page in
  event.from for full-page extensions (effective 10.31)\, and the Gift Card
  line_item_id field will become read-only in REST Admin API version 2027-0
 1 (noted 10.30). Additionally\, the Discounts Allocator Function API devel
 oper preview has ended.\n\nWhat to do: For Customer Account extensions\, u
 pdate handlers for currententrychange to use event.from for the previous p
 age. For Gift Card integrations\, remove any writes to line_item_id before
  upgrading to REST Admin API 2027-01.\n\nDetails: https://www.breakwatch.a
 i/radar/shopify/changes/shopify-breaks-currententrychange-event-makes-gift
 -card-line-1793685603902-731fc2b3
URL:https://www.breakwatch.ai/radar/shopify/changes/shopify-breaks-currente
 ntrychange-event-makes-gift-card-line-1793685603902-731fc2b3
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Shopify breaks currententrychange event and makes Gi
 ft Card line_item_id read-only in 2027-01
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:slack-1790316004277-fc3d22d2@breakwatch.ai
DTSTAMP:20260925T060004Z
DTSTART;VALUE=DATE:20270201
DTEND;VALUE=DATE:20270202
SUMMARY:Slack replaces assistant_view with agent_view in February 2027
DESCRIPTION:The assistant_view (Assistant messaging experience) will be dep
 recated in February 2027\, replaced by the new agent_view (Agent messaging
  experience) and the Agent Sessions API. Additionally\, system notificatio
 ns previously sent from Slackbot will now be sent from a new 'Slack' syste
 m user (USLACK)\, which is an immediate breaking change for apps that filt
 er by Slackbot's user ID.\n\nWhat to do: Migrate from assistant_view to ag
 ent_view using the provided migration guide\; update assistant.threads.set
 Status/assistant.threads.setTitle calls to the new Agent Sessions API (age
 nts.sessions.setStatus/agents.sessions.rename). Also update any integratio
 ns that filter by Slackbot's user ID or username to handle the new 'Slack'
  system user (USLACK) for system notifications.\n\nDetails: https://www.br
 eakwatch.ai/radar/slack/changes/slack-replaces-assistant-view-agent-view-f
 ebruary-2027-1790316004277-fc3d22d2
URL:https://www.breakwatch.ai/radar/slack/changes/slack-replaces-assistant-
 view-agent-view-february-2027-1790316004277-fc3d22d2
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Slack replaces assistant_view with agent_view in Feb
 ruary 2027
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:slack-1794873604377-52d4481e@breakwatch.ai
DTSTAMP:20261117T000004Z
DTSTART;VALUE=DATE:20270217
DTEND;VALUE=DATE:20270218
SUMMARY:Slack rejects GET and HEAD requests with a body starting Feb 17\, 2
 027
DESCRIPTION:On February 17\, 2027\, Slack's Web API will reject HTTP GET an
 d HEAD requests that include a request body with a 403 error. Many HTTP li
 braries silently attach a body to GET requests\, so apps using axios\, Guz
 zle\, Python requests\, or aiohttp may be affected without realizing it.\n
 \nWhat to do: Move all GET request parameters to the query string\, send t
 okens via the Authorization: Bearer header\, and ensure no request body is
  attached to GET/HEAD calls. Alternatively\, switch to POST requests. If u
 sing Slack CLI\, upgrade to v4.12.0+.\n\nDetails: https://www.breakwatch.a
 i/radar/slack/changes/slack-rejects-get-head-requests-body-starting-feb-17
 94873604377-52d4481e
URL:https://www.breakwatch.ai/radar/slack/changes/slack-rejects-get-head-re
 quests-body-starting-feb-1794873604377-52d4481e
CATEGORIES:Breaking change
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Slack rejects GET and HEAD requests with a body star
 ting Feb 17\, 2027
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-1791482404578-b19dd554@breakwatch.ai
DTSTAMP:20261008T180004Z
DTSTART;VALUE=DATE:20270226
DTEND;VALUE=DATE:20270227
SUMMARY:OpenAI retires whisper-1 and gpt-4o transcribe models on Feb 26\, 2
 027
DESCRIPTION:OpenAI announced the deprecation of whisper-1\, gpt-4o-transcri
 be\, gpt-4o-mini-transcribe\, and gpt-4o-transcribe-diarize (shutdown Febr
 uary 26\, 2027)\, and confirmed the Assistants API has already shut down a
 s of August 26\, 2026. Additionally\, reusable prompt objects\, the Evals 
 platform\, and Agent Builder deprecations were announced.\n\nWhat to do: M
 igrate transcription workloads from whisper-1/gpt-4o-transcribe variants t
 o gpt-live-transcribe or gpt-transcribe. Migrate Assistants API usage to t
 he Responses API and Conversations API using the provided migration guide.
 \n\nDetails: https://www.breakwatch.ai/radar/openai/changes/openai-retires
 -whisper-1-gpt-4o-transcribe-models-1791482404578-b19dd554
URL:https://www.breakwatch.ai/radar/openai/changes/openai-retires-whisper-1
 -gpt-4o-transcribe-models-1791482404578-b19dd554
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: OpenAI retires whisper-1 and gpt-4o transcribe model
 s on Feb 26\, 2027
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:shopify-1787594405613-90b7ee54@breakwatch.ai
DTSTAMP:20260824T180005Z
DTSTART;VALUE=DATE:20270301
DTEND;VALUE=DATE:20270302
SUMMARY:Shopify stops running script tags on Mar 1\, 2027
DESCRIPTION:Script tags are deprecated as of August 24\, 2026 and will stop
  running entirely on March 1\, 2027. This is a new entry added to the chan
 gelog requiring action from app developers who rely on script tags.\n\nWha
 t to do: Migrate away from Script Tags before March 1\, 2027. Consider usi
 ng Theme App Extensions or other supported injection mechanisms instead.\n
 \nDetails: https://www.breakwatch.ai/radar/shopify/changes/shopify-stops-r
 unning-script-tags-mar-1-2027-1787594405613-90b7ee54
URL:https://www.breakwatch.ai/radar/shopify/changes/shopify-stops-running-s
 cript-tags-mar-1-2027-1787594405613-90b7ee54
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: Shopify stops running script tags on Mar 1\, 2027
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:hubspot-1789495203426-7b34c405@breakwatch.ai
DTSTAMP:20260915T180003Z
DTSTART;VALUE=DATE:20270901
DTEND;VALUE=DATE:20270902
SUMMARY:HubSpot ends support for v1-v3 APIs and legacy apps in September 20
 27
DESCRIPTION:HubSpot announced at Fall Spotlight 2026 the end of support for
  v1-v3 APIs\, legacy public apps\, and legacy private apps\, all with a Se
 ptember 2027 enforcement date. This is a sweeping deprecation affecting a 
 large portion of the HubSpot API surface.\n\nWhat to do: Audit all integra
 tions using v1-v3 APIs\, legacy public apps\, or legacy private apps and m
 igrate to current supported versions (date-based versioning\, Developer Pl
 atform Projects) before September 2027.\n\nDetails: https://www.breakwatch
 .ai/radar/hubspot/changes/hubspot-ends-support-v1-v3-apis-legacy-apps-1789
 495203426-7b34c405
URL:https://www.breakwatch.ai/radar/hubspot/changes/hubspot-ends-support-v1
 -v3-apis-legacy-apps-1789495203426-7b34c405
CATEGORIES:Deprecation
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-P7D
DESCRIPTION:In a week: HubSpot ends support for v1-v3 APIs and legacy apps 
 in September 2027
END:VALARM
END:VEVENT
END:VCALENDAR
