shapi-cli 0.0.0-stage → 0.2.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,3 +1,50 @@
-# Temporary Holding Version
+# shapi-cli
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+**Find the code that breaks when a third-party API changes, and fix it test-first.**
+
+Third-party APIs change behaviour without a new version: GitHub's `workflow_dispatch` started answering `200` instead of `204`, QuickBooks stopped honouring old minor versions, HubSpot retired its v1 pipelines. Code that depended on the old behaviour breaks quietly. `shapi` maps every third-party API call in your repository, checks each one against an advisory database of real API changes, and repairs the ones it can, keeping a change only if a generated contract test fails before it and passes after it.
+
+## Quick start
+
+```sh
+npx shapi-cli scan .
+```
+
+`scan` reads your code and runs none of it. It prints the affected call sites, the API change behind each, and the deadline if there is one. Add `--out api.lock` to save the dependency map, or `--json` for machine-readable output.
+
+```sh
+npx shapi-cli fix .           # repair in a temporary copy and show the fix and its contract test
+npx shapi-cli fix . --write   # write the fix and the test into your working tree
+npx shapi-cli fix . --pr      # open a pull request (uses GITHUB_TOKEN or your gh login)
+```
+
+Install it to get the `shapi` command:
+
+```sh
+npm install -g shapi-cli
+shapi 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), 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.
+
+## How fixes are verified
+
+For every affected call site, `fix` generates a contract test that calls your code with the response it was written for and the response the provider sends now. The test must fail first. SHAPI then applies a deterministic recipe; with `--llm` and an `ANTHROPIC_API_KEY` it falls back to Claude. The change is kept only if the test then passes. Your repository is never modified unless you pass `--write` or `--pr`.
+
+## Requirements
+
+Node.js 22 or later.
+
+## More
+
+- Documentation: https://srivarshini09.github.io/YC/
+- 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
+
+## License
+
+Apache-2.0. The advisories in `advisories/` are also published, under CC BY 4.0, at https://github.com/SriVarshini09/shapi-advisories.

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/github-workflow-dispatch-204-to-200.json

@@ -0,0 +1,26 @@
+{
+  "id": "github-workflow-dispatch-204-to-200",
+  "provider": "github",
+  "title": "workflow_dispatch returns 200 with a body instead of 204",
+  "summary": "POST .../actions/workflows/{workflow_id}/dispatches started answering 200 OK with a JSON body (workflow run id) instead of 204 No Content. The OpenAPI schema and docs still said 204, and there was no changelog, version, or preview header. Clients that require exactly 204 treat a successful dispatch as a failure. GitHub later (2026-02-19) documented 200 as the response when return_run_details is set, and GitHub CLI v2.87.0+ sets it by default.",
+  "endpoint": {
+    "method": "POST",
+    "path": "/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches"
+  },
+  "changeClass": "status-code",
+  "trigger": {
+    "statusCodes": [204],
+    "newStatusCodes": [200]
+  },
+  "firstObserved": "2025-12-19",
+  "publishedNotice": null,
+  "effectiveDate": "2025-12-19",
+  "severity": "critical",
+  "migrationNote": "Treat both 200 and 204 as success (any 2xx). If you want the run id, send return_run_details: true and read it from the 200 body.",
+  "recipeId": "status-code-accept-set",
+  "sources": [
+    "https://stategraph.com/blog/github-broke-the-contract",
+    "https://github.blog/changelog/2026-02-19-workflow-dispatch-api-now-returns-run-ids"
+  ],
+  "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

@@ -0,0 +1,44 @@
+{
+  "id": "hubspot-pipelines-v1-sunset",
+  "provider": "hubspot",
+  "title": "Pipelines API v1 retired on 2026-12-04",
+  "summary": "HubSpot retires the legacy CRM Pipelines API v1 on 2026-12-04; after that, calls to v1 endpoints stop working. The replacement is the Pipelines API 2026-09 version (GA 2026-09-09). The /crm-pipelines/v1 path comes from HubSpot's legacy v1 reference; the notice itself names no paths.",
+  "endpoint": {
+    "method": "*",
+    "path": "/crm-pipelines/v1/**"
+  },
+  "changeClass": "version-sunset",
+  "trigger": {
+    "any": true
+  },
+  "firstObserved": null,
+  "publishedNotice": {
+    "date": "2026-08-14",
+    "url": "https://developers.hubspot.com/changelog/pipelines-api-v1-sunset"
+  },
+  "effectiveDate": "2026-12-04",
+  "severity": "high",
+  "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"
+}