shapi-cli 0.1.0 → 0.3.0

package/README.md

@@ -1,3 +1,5 @@
+<p align="center"><a href="https://shapi.dev/"><img src="https://raw.githubusercontent.com/SriVarshini09/YC/main/brand/png/shapi-lockup-horizontal-light-on-bg-1024.png" alt="SHAPI" width="320"></a></p>
+
 # shapi-cli
 
 **Find the code that breaks when a third-party API changes, and fix it test-first.**
@@ -22,12 +24,12 @@ Install it to get the `shapi` command:
 
 ```sh
 npm install -g shapi-cli
-shapi scan path/to/repo
+shapi scan path/to/repo        # or: shapi-cli scan path/to/repo
 ```
 
 ## What it checks
 
-- **Languages:** TypeScript and JavaScript (`fetch`, axios, got, undici, ky, node-fetch, and the official SDKs of the providers it knows).
+- **Languages:** TypeScript and JavaScript (`fetch`, axios, got, undici, ky, node-fetch, and the official SDKs of the providers it knows), and Python (`requests`, `httpx`, `aiohttp`, and the OpenAI, Anthropic, Stripe, Slack, Twilio and HubSpot SDKs). Fixes are for TypeScript and JavaScript; Python is scanned.
 - **Providers:** GitHub, Stripe, QuickBooks, Xero, HubSpot, Slack, OpenAI, Meta Graph and more.
 - **Advisories:** reviewed, open JSON advisories ship inside this package. Each one names the endpoint, what changed, when, and the evidence.
 
@@ -41,8 +43,9 @@ Node.js 22 or later.
 
 ## More
 
-- The GitHub App watches your repositories, posts a check on each push, and opens verified fix pull requests: https://github.com/SriVarshini09/YC
-- Report a problem: https://github.com/SriVarshini09/YC/issues
+- Documentation: https://shapi.dev/
+- The GitHub App watches your repositories, posts a check on each push, and opens verified fix pull requests: https://app.shapi.dev
+- Report a problem: https://github.com/SriVarshini09/shapi-advisories/issues or sri@shapi.dev
 
 ## License
 

package/advisories/anthropic-api-version-2026-10-21-sampling-params-400.json

@@ -0,0 +1,35 @@
+{
+  "id": "anthropic-api-version-2026-10-21-sampling-params-400",
+  "provider": "anthropic",
+  "title": "anthropic-version 2026-10-21 rejects temperature, top_p and top_k with 400",
+  "summary": "API version 2026-10-21 (released 2026-10-21 and sent by default by the new major SDK versions) removes temperature, top_p and top_k from the Messages API: any request that sends one of them returns 400, even at the default value. The same version also returns 400 for document blocks in assistant messages and for citations on user text blocks. Requests that stay on 2023-06-01 are unchanged.",
+  "endpoint": {
+    "method": "POST",
+    "path": "/v1/messages"
+  },
+  "changeClass": "status-code",
+  "trigger": {
+    "headers": [
+      {
+        "name": "anthropic-version",
+        "values": [
+          "2026-10-21"
+        ]
+      }
+    ]
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": "2026-10-21",
+    "url": "https://platform.claude.com/docs/en/release-notes/overview"
+  },
+  "effectiveDate": "2026-10-21",
+  "severity": "high",
+  "migrationNote": "Before sending anthropic-version: 2026-10-21 or upgrading to the new SDK majors (Python 2.0.0, TypeScript 1.0.0, Go 2.0.0, Java 3.0.0, Ruby 2.0.0, PHP 1.0.0, C# 13.0.0), remove temperature, top_p and top_k from Messages, token-counting and batch requests, move document blocks into user messages, and drop citations from user text blocks. If a request depends on a non-default temperature, keep that request on 2023-06-01.",
+  "sources": [
+    "https://platform.claude.com/docs/en/api/migration-2026-10-21",
+    "https://platform.claude.com/docs/en/api/versioning",
+    "https://platform.claude.com/docs/en/release-notes/overview"
+  ],
+  "status": "verified"
+}

package/advisories/google-ads-api-v22-sunset.json

@@ -0,0 +1,27 @@
+{
+  "id": "google-ads-api-v22-sunset",
+  "provider": "google",
+  "title": "Google Ads API v22 sunset on 2026-10-07",
+  "summary": "Google Ads API v22 was sunset on 2026-10-07; from that date all v22 requests fail. Code still pinned to /v22/ paths, or to client library versions that only speak v22, is broken.",
+  "endpoint": {
+    "method": "*",
+    "path": "/v22/**"
+  },
+  "changeClass": "version-sunset",
+  "trigger": {
+    "any": true
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": "2026-09-02",
+    "url": "https://ads-developers.googleblog.com/2026/09/google-ads-api-v22-sunset-reminder.html"
+  },
+  "effectiveDate": "2026-10-07",
+  "severity": "critical",
+  "migrationNote": "Change the version segment of googleads.googleapis.com paths to a supported version (v24 or later is safest, since v23 sunsets in February 2027), upgrade the client library, and work through each skipped version's breaking-changes list. The Google Ads API metrics page in the Cloud Console shows which versioned methods your project still calls.",
+  "sources": [
+    "https://ads-developers.googleblog.com/2026/09/google-ads-api-v22-sunset-reminder.html",
+    "https://developers.google.com/google-ads/api/docs/sunset-dates"
+  ],
+  "status": "verified"
+}

package/advisories/google-custom-search-json-api-shutdown.json

@@ -0,0 +1,27 @@
+{
+  "id": "google-custom-search-json-api-shutdown",
+  "provider": "google",
+  "title": "Custom Search JSON API discontinued on 2027-01-01",
+  "summary": "The Custom Search JSON API is closed to new customers, and existing customers have until 2027-01-01 to move off it; Google calls that date the service discontinuation. After that, calls to /customsearch/v1 stop working.",
+  "endpoint": {
+    "method": "GET",
+    "path": "/customsearch/v1/**"
+  },
+  "changeClass": "version-sunset",
+  "trigger": {
+    "any": true
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": null,
+    "url": "https://developers.google.com/custom-search/v1/overview"
+  },
+  "effectiveDate": "2027-01-01",
+  "severity": "critical",
+  "migrationNote": "Replace calls to www.googleapis.com/customsearch/v1 before 2027-01-01: Google points to Vertex AI Search for searching up to 50 domains, and to its interest form for full-web search. Expect a different request format, response shape and pricing.",
+  "sources": [
+    "https://developers.google.com/custom-search/v1/overview",
+    "https://developers.google.com/custom-search/v1/using_rest"
+  ],
+  "status": "verified"
+}

package/advisories/google-gemini-2-0-flash-shutdown.json

@@ -0,0 +1,27 @@
+{
+  "id": "google-gemini-2-0-flash-shutdown",
+  "provider": "google-gemini",
+  "title": "gemini-2.0-flash and gemini-2.0-flash-lite shut down on 2026-06-01",
+  "summary": "Google shut down gemini-2.0-flash, gemini-2.0-flash-001, gemini-2.0-flash-lite and gemini-2.0-flash-lite-001 on 2026-06-01. A shut-down model is completely turned off, so generateContent and streamGenerateContent calls that name it in the path fail. Calls that pass the model in a request body (as /v1beta/interactions does) or in a variable are not matched by this path.",
+  "endpoint": {
+    "method": "POST",
+    "path": "/*/models/gemini-2.0-flash*:*"
+  },
+  "changeClass": "version-sunset",
+  "trigger": {
+    "any": true
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": null,
+    "url": "https://ai.google.dev/gemini-api/docs/deprecations"
+  },
+  "effectiveDate": "2026-06-01",
+  "severity": "critical",
+  "migrationNote": "Change the model segment to gemini-3.6-flash (for gemini-2.0-flash) or gemini-3.1-flash-lite (for gemini-2.0-flash-lite), for example /v1beta/models/gemini-3.6-flash:generateContent, and re-test prompts and output parsing.",
+  "sources": [
+    "https://ai.google.dev/gemini-api/docs/deprecations",
+    "https://ai.google.dev/api/generate-content"
+  ],
+  "status": "verified"
+}

package/advisories/google-gemini-2-5-flash-image-shutdown.json

@@ -0,0 +1,27 @@
+{
+  "id": "google-gemini-2-5-flash-image-shutdown",
+  "provider": "google-gemini",
+  "title": "gemini-2.5-flash-image shuts down on 2027-03-15",
+  "summary": "Google shuts down gemini-2.5-flash-image (the original Nano Banana image model) on 2027-03-15. After that the model is turned off and generateContent calls that name it in the path fail. Calls that pass the model in a request body are not matched by this path.",
+  "endpoint": {
+    "method": "POST",
+    "path": "/*/models/gemini-2.5-flash-image:*"
+  },
+  "changeClass": "version-sunset",
+  "trigger": {
+    "any": true
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": null,
+    "url": "https://ai.google.dev/gemini-api/docs/deprecations"
+  },
+  "effectiveDate": "2027-03-15",
+  "severity": "high",
+  "migrationNote": "Move image generation to gemini-3.1-flash-lite-image, the replacement on the deprecations page, before 2027-03-15, and re-test how you read the returned image parts.",
+  "sources": [
+    "https://ai.google.dev/gemini-api/docs/deprecations",
+    "https://ai.google.dev/gemini-api/docs/image-generation"
+  ],
+  "status": "verified"
+}

package/advisories/google-gemini-2-5-preview-tts-shutdown.json

@@ -0,0 +1,27 @@
+{
+  "id": "google-gemini-2-5-preview-tts-shutdown",
+  "provider": "google-gemini",
+  "title": "Gemini 2.5 preview TTS models shut down on 2026-11-17",
+  "summary": "Google shuts down gemini-2.5-flash-preview-tts and gemini-2.5-pro-preview-tts on 2026-11-17. After that the models are turned off and speech-generation calls that name them in the path fail. Calls that pass the model in a request body are not matched by this path.",
+  "endpoint": {
+    "method": "POST",
+    "path": "/*/models/gemini-2.5-*-preview-tts:*"
+  },
+  "changeClass": "version-sunset",
+  "trigger": {
+    "any": true
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": null,
+    "url": "https://ai.google.dev/gemini-api/docs/deprecations"
+  },
+  "effectiveDate": "2026-11-17",
+  "severity": "critical",
+  "migrationNote": "Switch to gemini-3.8-flash-tts or gemini-3.8-flash-lite-tts before 2026-11-17; the current speech-generation docs send the model in the body of POST /v1beta/interactions. Re-check voice names and how you decode the returned audio.",
+  "sources": [
+    "https://ai.google.dev/gemini-api/docs/deprecations",
+    "https://ai.google.dev/gemini-api/docs/speech-generation"
+  ],
+  "status": "verified"
+}

package/advisories/hubspot-contact-lists-v1-sunset.json

@@ -0,0 +1,28 @@
+{
+  "id": "hubspot-contact-lists-v1-sunset",
+  "provider": "hubspot",
+  "title": "Contact Lists API v1 retired on 2026-04-30; endpoints return 404",
+  "summary": "HubSpot sunset the v1 Contact Lists API on 2026-04-30 (moved from 2025-09-30). Since then the /contacts/v1/lists endpoints for creating, updating, deleting and reading lists and list contacts return HTTP 404. The replacement is the Lists API (2026-03 or v3), which uses a new listId instead of the v1 legacyListId.",
+  "endpoint": {
+    "method": "*",
+    "path": "/contacts/v1/lists/**"
+  },
+  "changeClass": "version-sunset",
+  "trigger": {
+    "any": true
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": "2025-09-12",
+    "url": "https://developers.hubspot.com/changelog/extension-contact-lists-api-v1-sunset-moved-to-april-30-2026"
+  },
+  "effectiveDate": "2026-04-30",
+  "severity": "critical",
+  "migrationNote": "Map each stored legacyListId to the new listId with GET /crm/lists/2026-03/idmapping?legacyListId=... (or POST /crm/lists/2026-03/idmapping for up to 10,000 ids; ids in missingLegacyListIds no longer exist), then move reads to GET /crm/lists/2026-03/{listId} and /crm/lists/2026-03/{listId}/memberships, and membership writes to PUT /crm/lists/2026-03/{listId}/memberships/add, /remove or /add-and-remove. The legacy GET /v1/lists/{legacyListId}/sizeAndEditsHistory/between endpoint was retired too and is not covered by this path pattern.",
+  "sources": [
+    "https://developers.hubspot.com/changelog/extension-contact-lists-api-v1-sunset-moved-to-april-30-2026",
+    "https://developers.hubspot.com/docs/api-reference/legacy/crm/lists/v1-list-api-migration-guide",
+    "https://developers.hubspot.com/docs/api-reference/latest/deprecated-apis"
+  ],
+  "status": "verified"
+}

package/advisories/hubspot-contacts-v1-list-memberships-removed.json

@@ -0,0 +1,30 @@
+{
+  "id": "hubspot-contacts-v1-list-memberships-removed",
+  "provider": "hubspot",
+  "title": "v1 contact read endpoints stopped returning list memberships on 2026-04-30",
+  "summary": "With the Contact Lists v1 sunset, six v1 contact read endpoints (get by vid, email or utk, and their batch versions) keep working but, since 2026-04-30, no longer return list memberships. The field in the v1 response is list-memberships (requested with showListMemberships); code that reads it now gets no membership data, without an error.",
+  "endpoint": {
+    "method": "GET",
+    "path": "/contacts/v1/contact/**"
+  },
+  "changeClass": "field-rename",
+  "trigger": {
+    "fields": [
+      "list-memberships"
+    ]
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": "2025-09-12",
+    "url": "https://developers.hubspot.com/changelog/extension-contact-lists-api-v1-sunset-moved-to-april-30-2026"
+  },
+  "effectiveDate": "2026-04-30",
+  "severity": "high",
+  "migrationNote": "Stop reading list-memberships from /contacts/v1/contact/... responses. Map stored legacy list ids to new list ids with /crm/lists/2026-03/idmapping, then read list members from GET /crm/lists/2026-03/{listId}/memberships (results ordered by record id) and build the contact-to-list mapping from that, or move contact reads to the current CRM objects API together with the Lists API.",
+  "sources": [
+    "https://developers.hubspot.com/docs/api-reference/legacy/crm/lists/v1-list-api-migration-guide",
+    "https://developers.hubspot.com/changelog/extension-contact-lists-api-v1-sunset-moved-to-april-30-2026",
+    "https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/contacts/v1/get-contacts-v1-contactvidvid-profile.md"
+  ],
+  "status": "verified"
+}

package/advisories/hubspot-marketing-emails-folderid-removed.json

@@ -0,0 +1,39 @@
+{
+  "id": "hubspot-marketing-emails-folderid-removed",
+  "provider": "hubspot",
+  "title": "Marketing Email v3 stopped returning folderId on 2026-01-28",
+  "summary": "HubSpot moved marketing email folders to a v2 folder system and added folderIdV2 to Marketing Email v3 responses. Both fields were returned side by side until folderId was removed on 2026-01-28; since then only folderIdV2 is returned, so code keyed on folderId gets no folder value.",
+  "endpoint": {
+    "method": "GET",
+    "path": "/marketing/v3/emails/**"
+  },
+  "changeClass": "field-rename",
+  "trigger": {
+    "fields": [
+      "folderId",
+      "results[].folderId"
+    ]
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": "2025-10-30",
+    "url": "https://developers.hubspot.com/changelog/marketing-email-api-folder-id-migration"
+  },
+  "effectiveDate": "2026-01-28",
+  "severity": "high",
+  "migrationNote": "Read folderIdV2 instead of folderId from /marketing/v3/emails responses and re-key any stored folder index on folderIdV2 (list emails with folderId__not_null to rebuild it); old folderId values no longer match anything the API returns.",
+  "recipeId": "apply-fix",
+  "fix": {
+    "fields": [
+      {
+        "from": "folderId",
+        "to": "folderIdV2"
+      }
+    ]
+  },
+  "sources": [
+    "https://developers.hubspot.com/changelog/marketing-email-api-folder-id-migration",
+    "https://developers.hubspot.com/docs/api-reference/marketing-marketing-emails-v3/marketing-emails/get-marketing-v3-emails-"
+  ],
+  "status": "verified"
+}

package/advisories/hubspot-marketing-emails-v1-sunset.json

@@ -0,0 +1,24 @@
+{
+  "id": "hubspot-marketing-emails-v1-sunset",
+  "provider": "hubspot",
+  "title": "Marketing Email API v1 sunset (reported as 2025-11-01)",
+  "summary": "HubSpot replaced the v1 Marketing Email API (/marketing-emails/v1/...) with the Marketing Email v3 API. HubSpot's own folder-ID post calls v1 \"being sunset\" and CData reports the endpoint as sunset; search snippets of HubSpot's (now 404) changelog post put the sunset on 2025-11-01, but that date could not be read on an open page.",
+  "endpoint": {
+    "method": "*",
+    "path": "/marketing-emails/v1/**"
+  },
+  "changeClass": "version-sunset",
+  "trigger": {
+    "any": true
+  },
+  "firstObserved": null,
+  "publishedNotice": null,
+  "effectiveDate": "2025-11-01",
+  "severity": "critical",
+  "migrationNote": "Move email calls from /marketing-emails/v1/emails to the Marketing Email v3 API (POST /marketing/v3/emails to create, GET /marketing/v3/emails to list, GET /marketing/v3/emails/{emailId} to read one) and read folders from folderIdV2. Search snippets say other legacy email APIs, such as email analytics, were not part of this sunset.",
+  "sources": [
+    "https://developers.hubspot.com/changelog/marketing-email-api-folder-id-migration",
+    "https://cdn.cdata.com/help/DHN/ado/pg_deprecationnotices.htm"
+  ],
+  "status": "unverified"
+}

package/advisories/hubspot-pipelines-v1-sunset.json

@@ -18,7 +18,27 @@
   },
   "effectiveDate": "2026-12-04",
   "severity": "high",
-  "migrationNote": "Migrate to the Pipelines API 2026-09 (or 2026-03 or newer) endpoints before 2026-12-04.",
-  "sources": ["https://developers.hubspot.com/changelog/pipelines-api-v1-sunset"],
+  "migrationNote": "Call GET /crm/pipelines/2026-09/{objectType} (HubSpot's OpenAPI spec for the 2026-09 Pipelines API) instead of /crm-pipelines/v1/pipelines/{objectType} before 2026-12-04. The response keeps results[] and stages[], but pipelines and stages are identified by id instead of pipelineId and stageId.",
+  "recipeId": "apply-fix",
+  "fix": {
+    "path": {
+      "from": "/crm-pipelines/v1/pipelines/",
+      "to": "/crm/pipelines/2026-09/"
+    },
+    "fields": [
+      {
+        "from": "results[].pipelineId",
+        "to": "results[].id"
+      },
+      {
+        "from": "results[].stages[].stageId",
+        "to": "results[].stages[].id"
+      }
+    ]
+  },
+  "sources": [
+    "https://developers.hubspot.com/docs/api-reference/latest/crm/pipelines/guide",
+    "https://github.com/HubSpot/HubSpot-public-api-spec-collection/blob/main/PublicApiSpecs/CRM/Pipelines/Rollouts/145896/2026-09/pipelines.json"
+  ],
   "status": "verified"
 }

package/advisories/meta-graph-commerce-order-management-removed.json

@@ -0,0 +1,26 @@
+{
+  "id": "meta-graph-commerce-order-management-removed",
+  "provider": "meta-graph",
+  "title": "Commerce Order Management API removed on all versions on 2026-10-27",
+  "summary": "Meta deprecated the Commerce Order Management API (47 endpoints, including GET /{page-id}/commerce_orders and GET /{commerce-merchant-settings-id}/commerce_orders) with no replacement. Calls on v26.0+ are blocked since 2026-07-29, and the endpoints are removed from all remaining versions on 2026-10-27. Order sub-resources (items, shipments, refunds, cancellations, payments, tax_settings) by object id go too, but only the commerce_orders list edge is matched here.",
+  "endpoint": {
+    "method": "GET",
+    "path": "/*/*/commerce_orders"
+  },
+  "changeClass": "version-sunset",
+  "trigger": {
+    "any": true
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": "2026-07-29",
+    "url": "https://developers.facebook.com/docs/graph-api/changelog/version26.0"
+  },
+  "effectiveDate": "2026-10-27",
+  "severity": "critical",
+  "migrationNote": "There is no replacement API. Stop calling commerce_orders, commerce_returns, tax_settings and the order, shipment, refund and cancellation object reads, and handle orders in Commerce Manager or your own order system. Guard any remaining calls so the error does not break sync jobs.",
+  "sources": [
+    "https://developers.facebook.com/docs/graph-api/changelog/version26.0"
+  ],
+  "status": "verified"
+}

package/advisories/meta-graph-date-format-param-removed.json

@@ -0,0 +1,30 @@
+{
+  "id": "meta-graph-date-format-param-removed",
+  "provider": "meta-graph",
+  "title": "date_format query parameter returns an error from 2026-10-27",
+  "summary": "Requests that include the legacy date_format parameter return an error on Graph API v26.0+ since 2026-07-29 and on all supported versions from 2026-10-27. The same change makes pretty and debug ignored and removes ETag/304 Not Modified behaviour.",
+  "endpoint": {
+    "method": "*",
+    "path": "/**"
+  },
+  "changeClass": "version-sunset",
+  "trigger": {
+    "query": [
+      {
+        "name": "date_format"
+      }
+    ]
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": "2026-07-29",
+    "url": "https://developers.facebook.com/docs/graph-api/changelog/version26.0"
+  },
+  "effectiveDate": "2026-10-27",
+  "severity": "critical",
+  "migrationNote": "Remove date_format from every Graph API request and parse the default ISO 8601 timestamps in your own code. While you are there, drop any reliance on If-None-Match/304 caching and on pretty or debug output.",
+  "sources": [
+    "https://developers.facebook.com/docs/graph-api/changelog/version26.0"
+  ],
+  "status": "verified"
+}

package/advisories/meta-graph-delivery-estimate-fields-removed.json

@@ -0,0 +1,30 @@
+{
+  "id": "meta-graph-delivery-estimate-fields-removed",
+  "provider": "meta-graph",
+  "title": "Delivery Estimate drops daily_outcomes_curve, budget_guardrail and estimate_dau",
+  "summary": "The daily_outcomes_curve, budget_guardrail and estimate_dau fields are removed from GET /{ad-account-id}/delivery_estimate and GET /{adset-id}/delivery_estimate responses because the service behind them was shut down. The removal applies to Marketing API v26.0 and to all remaining versions on 2026-10-27; the calls still succeed but the fields are missing.",
+  "endpoint": {
+    "method": "GET",
+    "path": "/*/*/delivery_estimate"
+  },
+  "changeClass": "field-rename",
+  "trigger": {
+    "fields": [
+      "daily_outcomes_curve",
+      "budget_guardrail",
+      "estimate_dau"
+    ]
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": "2026-07-29",
+    "url": "https://developers.facebook.com/docs/graph-api/changelog/version26.0"
+  },
+  "effectiveDate": "2026-10-27",
+  "severity": "critical",
+  "migrationNote": "Stop requesting and reading daily_outcomes_curve, budget_guardrail and estimate_dau; treat them as absent. Meta offers no replacement, so remove any forecasting or budget UI that depends on them or derive it from the remaining estimate fields.",
+  "sources": [
+    "https://developers.facebook.com/docs/graph-api/changelog/version26.0"
+  ],
+  "status": "verified"
+}

package/advisories/meta-graph-instagram-oembed-fields-removed.json

@@ -0,0 +1,33 @@
+{
+  "id": "meta-graph-instagram-oembed-fields-removed",
+  "provider": "meta-graph",
+  "title": "oEmbed responses no longer return author and thumbnail fields",
+  "summary": "Since 2025-11-03, on all API versions, Instagram post oEmbed responses (GET /{version}/instagram_oembed) no longer include author_name, author_url, thumbnail_url, thumbnail_width or thumbnail_height. The same fields were removed from Facebook post and video oEmbed (oembed_post, oembed_video), and the Facebook page oEmbed endpoint was deprecated.",
+  "endpoint": {
+    "method": "GET",
+    "path": "/*/instagram_oembed"
+  },
+  "changeClass": "field-rename",
+  "trigger": {
+    "fields": [
+      "author_name",
+      "author_url",
+      "thumbnail_url",
+      "thumbnail_width",
+      "thumbnail_height"
+    ]
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": "2025-04-08",
+    "url": "https://developers.facebook.com/docs/instagram-platform/changelog"
+  },
+  "effectiveDate": "2025-11-03",
+  "severity": "high",
+  "migrationNote": "Stop reading author and thumbnail fields from oEmbed and render the returned html instead. If you need a thumbnail or author, read them from the Instagram Graph API media object for media your app can access, and treat the oEmbed fields as absent.",
+  "sources": [
+    "https://developers.facebook.com/docs/instagram-platform/changelog",
+    "https://developers.facebook.com/docs/instagram-platform/oembed"
+  ],
+  "status": "verified"
+}

package/advisories/meta-graph-marketing-api-v24-sunset.json

@@ -0,0 +1,34 @@
+{
+  "id": "meta-graph-marketing-api-v24-sunset",
+  "provider": "meta-graph",
+  "title": "Marketing API v24.0 available until 2026-11-10",
+  "summary": "Marketing API v24.0 is available until 2026-11-10, much earlier than Graph API v24.0. After that, ads calls pinned to v24.0 either fail or are auto-upgraded to the next version; endpoints that changed between versions fail. This matches ad account edges (/v24.0/act_{id}/...); calls to campaign, ad set and ad objects by numeric id on v24.0 are affected too but cannot be told apart from other Graph calls by path.",
+  "endpoint": {
+    "method": "*",
+    "path": "/v24.0/act_*/**"
+  },
+  "changeClass": "version-sunset",
+  "trigger": {
+    "any": true
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": null,
+    "url": "https://developers.facebook.com/docs/marketing-api/marketing-api-changelog/"
+  },
+  "effectiveDate": "2026-11-10",
+  "severity": "critical",
+  "migrationNote": "Move all Marketing API calls (ad accounts, campaigns, ad sets, ads, creatives, insights) to v25.0 or, better, v26.0, and re-test against the v25.0 and v26.0 changelogs (for example the Advantage+ campaign and targeting_automation changes) before 2026-11-10.",
+  "recipeId": "apply-fix",
+  "fix": {
+    "path": {
+      "from": "/v24.0/",
+      "to": "/v26.0/"
+    }
+  },
+  "sources": [
+    "https://developers.facebook.com/docs/marketing-api/marketing-api-changelog/",
+    "https://developers.facebook.com/documentation/ads-commerce/marketing-api/overview/versioning"
+  ],
+  "status": "verified"
+}

package/advisories/meta-graph-marketing-api-v25-sunset.json

@@ -0,0 +1,35 @@
+{
+  "id": "meta-graph-marketing-api-v25-sunset",
+  "provider": "meta-graph",
+  "title": "Marketing API v25.0 available until 2027-02-23",
+  "summary": "Marketing API v25.0 is available until 2027-02-23 (Graph API v25.0 itself runs to 2028). After that, ads calls pinned to v25.0 fail or are auto-upgraded, and endpoints that changed in v26.0 fail. Meta also says the explicit targeting_automation.advantage_audience flag becomes mandatory on all versions once v25.0 is deprecated.",
+  "endpoint": {
+    "method": "*",
+    "path": "/v25.0/act_*/**"
+  },
+  "changeClass": "version-sunset",
+  "trigger": {
+    "any": true
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": null,
+    "url": "https://developers.facebook.com/docs/marketing-api/marketing-api-changelog/"
+  },
+  "effectiveDate": "2027-02-23",
+  "severity": "high",
+  "migrationNote": "Upgrade Marketing API calls to v26.0, set targeting_automation.advantage_audience to 1 or 0 explicitly on ad set targeting, and review the v26.0 changelog (poll ads, Messenger Stories, Explore placement, delivery estimate fields) before 2027-02-23.",
+  "recipeId": "apply-fix",
+  "fix": {
+    "path": {
+      "from": "/v25.0/",
+      "to": "/v26.0/"
+    }
+  },
+  "sources": [
+    "https://developers.facebook.com/docs/marketing-api/marketing-api-changelog/",
+    "https://developers.facebook.com/documentation/ads-commerce/marketing-api/overview/versioning",
+    "https://developers.facebook.com/docs/graph-api/changelog/version26.0"
+  ],
+  "status": "verified"
+}

package/advisories/meta-graph-page-insights-impressions-fans-removed.json

@@ -0,0 +1,51 @@
+{
+  "id": "meta-graph-page-insights-impressions-fans-removed",
+  "provider": "meta-graph",
+  "title": "Page Insights impressions and page fans metrics removed on 2025-11-15",
+  "summary": "Since 2025-11-15, on all API versions, requesting the Page and post impressions metrics (page_impressions, page_impressions_paid, page_impressions_viral, page_impressions_nonviral, post_impressions, post_impressions_paid, post_impressions_fan, post_impressions_organic, post_impressions_viral, post_impressions_nonviral) or the fans metrics (page_fans, page_fans_locale, page_fans_city, page_fans_country, page_fan_adds, page_fan_adds_unique, page_fan_removes, page_fan_removes_unique) returns an invalid metric error. SHAPI flags calls that request one of these metrics.",
+  "endpoint": {
+    "method": "GET",
+    "path": "/*/*/insights"
+  },
+  "changeClass": "version-sunset",
+  "trigger": {
+    "query": [
+      {
+        "name": "metric",
+        "values": [
+          "page_fans",
+          "page_fans_locale",
+          "page_fans_city",
+          "page_fans_country",
+          "page_fan_adds",
+          "page_fan_adds_unique",
+          "page_fan_removes",
+          "page_fan_removes_unique",
+          "page_impressions",
+          "page_impressions_paid",
+          "page_impressions_viral",
+          "page_impressions_nonviral",
+          "post_impressions",
+          "post_impressions_paid",
+          "post_impressions_fan",
+          "post_impressions_organic",
+          "post_impressions_viral",
+          "post_impressions_nonviral"
+        ]
+      }
+    ]
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": "2025-08-15",
+    "url": "https://developers.facebook.com/blog/post/2025/08/15/page-insights-api-updates/"
+  },
+  "effectiveDate": "2025-11-15",
+  "severity": "critical",
+  "migrationNote": "Replace page_impressions with page_media_view and post_impressions with post_media_view (use the is_from_ads or is_from_followers breakdowns for the paid, organic and fan splits), and replace page_fans/page_fans_city/page_fans_country with page_follows/page_follows_city/page_follows_country. Remove the other listed metrics; one invalid metric fails the whole insights request.",
+  "sources": [
+    "https://developers.facebook.com/blog/post/2025/08/15/page-insights-api-updates/",
+    "https://developers.facebook.com/docs/platforminsights/page/deprecated-metrics"
+  ],
+  "status": "verified"
+}