shapi-cli 0.0.0-stage → 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +202 -0
- package/README.md +48 -2
- package/advisories/github-workflow-dispatch-204-to-200.json +26 -0
- package/advisories/hubspot-pipelines-v1-sunset.json +24 -0
- package/advisories/meta-graph-v20-sunset.json +24 -0
- package/advisories/meta-graph-v21-sunset.json +24 -0
- package/advisories/quickbooks-minorversion-below-75-ignored.json +28 -0
- package/advisories/reddit-logged-out-json-403.json +25 -0
- package/advisories/xero-accounting-transactions-scope-split.json +27 -0
- package/bin/shapi.js +4 -0
- package/dist/index.js +3026 -0
- package/package.json +51 -4
- package/recordings/github-workflow-dispatch-204-to-200.json +46 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/README.md
CHANGED
|
@@ -1,3 +1,49 @@
|
|
|
1
|
-
#
|
|
1
|
+
# shapi-cli
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
**Find the code that breaks when a third-party API changes, and fix it test-first.**
|
|
4
|
+
|
|
5
|
+
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.
|
|
6
|
+
|
|
7
|
+
## Quick start
|
|
8
|
+
|
|
9
|
+
```sh
|
|
10
|
+
npx shapi-cli scan .
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
`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.
|
|
14
|
+
|
|
15
|
+
```sh
|
|
16
|
+
npx shapi-cli fix . # repair in a temporary copy and show the fix and its contract test
|
|
17
|
+
npx shapi-cli fix . --write # write the fix and the test into your working tree
|
|
18
|
+
npx shapi-cli fix . --pr # open a pull request (uses GITHUB_TOKEN or your gh login)
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
Install it to get the `shapi` command:
|
|
22
|
+
|
|
23
|
+
```sh
|
|
24
|
+
npm install -g shapi-cli
|
|
25
|
+
shapi scan path/to/repo
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
## What it checks
|
|
29
|
+
|
|
30
|
+
- **Languages:** TypeScript and JavaScript (`fetch`, axios, got, undici, ky, node-fetch, and the official SDKs of the providers it knows).
|
|
31
|
+
- **Providers:** GitHub, Stripe, QuickBooks, Xero, HubSpot, Slack, OpenAI, Meta Graph and more.
|
|
32
|
+
- **Advisories:** reviewed, open JSON advisories ship inside this package. Each one names the endpoint, what changed, when, and the evidence.
|
|
33
|
+
|
|
34
|
+
## How fixes are verified
|
|
35
|
+
|
|
36
|
+
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`.
|
|
37
|
+
|
|
38
|
+
## Requirements
|
|
39
|
+
|
|
40
|
+
Node.js 22 or later.
|
|
41
|
+
|
|
42
|
+
## More
|
|
43
|
+
|
|
44
|
+
- The GitHub App watches your repositories, posts a check on each push, and opens verified fix pull requests: https://github.com/SriVarshini09/YC
|
|
45
|
+
- Report a problem: https://github.com/SriVarshini09/YC/issues
|
|
46
|
+
|
|
47
|
+
## License
|
|
48
|
+
|
|
49
|
+
Apache-2.0. The advisories in `advisories/` are also published, under CC BY 4.0, at https://github.com/SriVarshini09/shapi-advisories.
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "github-workflow-dispatch-204-to-200",
|
|
3
|
+
"provider": "github",
|
|
4
|
+
"title": "workflow_dispatch returns 200 with a body instead of 204",
|
|
5
|
+
"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.",
|
|
6
|
+
"endpoint": {
|
|
7
|
+
"method": "POST",
|
|
8
|
+
"path": "/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches"
|
|
9
|
+
},
|
|
10
|
+
"changeClass": "status-code",
|
|
11
|
+
"trigger": {
|
|
12
|
+
"statusCodes": [204],
|
|
13
|
+
"newStatusCodes": [200]
|
|
14
|
+
},
|
|
15
|
+
"firstObserved": "2025-12-19",
|
|
16
|
+
"publishedNotice": null,
|
|
17
|
+
"effectiveDate": "2025-12-19",
|
|
18
|
+
"severity": "critical",
|
|
19
|
+
"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.",
|
|
20
|
+
"recipeId": "status-code-accept-set",
|
|
21
|
+
"sources": [
|
|
22
|
+
"https://stategraph.com/blog/github-broke-the-contract",
|
|
23
|
+
"https://github.blog/changelog/2026-02-19-workflow-dispatch-api-now-returns-run-ids"
|
|
24
|
+
],
|
|
25
|
+
"status": "verified"
|
|
26
|
+
}
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "hubspot-pipelines-v1-sunset",
|
|
3
|
+
"provider": "hubspot",
|
|
4
|
+
"title": "Pipelines API v1 retired on 2026-12-04",
|
|
5
|
+
"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.",
|
|
6
|
+
"endpoint": {
|
|
7
|
+
"method": "*",
|
|
8
|
+
"path": "/crm-pipelines/v1/**"
|
|
9
|
+
},
|
|
10
|
+
"changeClass": "version-sunset",
|
|
11
|
+
"trigger": {
|
|
12
|
+
"any": true
|
|
13
|
+
},
|
|
14
|
+
"firstObserved": null,
|
|
15
|
+
"publishedNotice": {
|
|
16
|
+
"date": "2026-08-14",
|
|
17
|
+
"url": "https://developers.hubspot.com/changelog/pipelines-api-v1-sunset"
|
|
18
|
+
},
|
|
19
|
+
"effectiveDate": "2026-12-04",
|
|
20
|
+
"severity": "high",
|
|
21
|
+
"migrationNote": "Migrate to the Pipelines API 2026-09 (or 2026-03 or newer) endpoints before 2026-12-04.",
|
|
22
|
+
"sources": ["https://developers.hubspot.com/changelog/pipelines-api-v1-sunset"],
|
|
23
|
+
"status": "verified"
|
|
24
|
+
}
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "meta-graph-v20-sunset",
|
|
3
|
+
"provider": "meta-graph",
|
|
4
|
+
"title": "Graph API v20.0 removed; calls fall forward to the next version",
|
|
5
|
+
"summary": "Graph API v20.0 was deprecated and removed on 2026-09-24. Calls pinned to v20.0 do not fail: they are served by the next oldest usable version, so response shapes can change silently.",
|
|
6
|
+
"endpoint": {
|
|
7
|
+
"method": "*",
|
|
8
|
+
"path": "/v20.0/**"
|
|
9
|
+
},
|
|
10
|
+
"changeClass": "version-sunset",
|
|
11
|
+
"trigger": {
|
|
12
|
+
"any": true
|
|
13
|
+
},
|
|
14
|
+
"firstObserved": null,
|
|
15
|
+
"publishedNotice": {
|
|
16
|
+
"date": null,
|
|
17
|
+
"url": "https://developers.facebook.com/docs/graph-api/changelog/versions"
|
|
18
|
+
},
|
|
19
|
+
"effectiveDate": "2026-09-24",
|
|
20
|
+
"severity": "high",
|
|
21
|
+
"migrationNote": "Move the version segment to a supported version (v22.0 or later) and re-test the fields you read.",
|
|
22
|
+
"sources": ["https://developers.facebook.com/docs/graph-api/changelog/versions"],
|
|
23
|
+
"status": "verified"
|
|
24
|
+
}
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "meta-graph-v21-sunset",
|
|
3
|
+
"provider": "meta-graph",
|
|
4
|
+
"title": "Graph API v21.0 removed on 2027-01-21",
|
|
5
|
+
"summary": "Graph API v21.0 is deprecated and removed on 2027-01-21. After that, calls pinned to v21.0 are served by the next oldest usable version without an error.",
|
|
6
|
+
"endpoint": {
|
|
7
|
+
"method": "*",
|
|
8
|
+
"path": "/v21.0/**"
|
|
9
|
+
},
|
|
10
|
+
"changeClass": "version-sunset",
|
|
11
|
+
"trigger": {
|
|
12
|
+
"any": true
|
|
13
|
+
},
|
|
14
|
+
"firstObserved": null,
|
|
15
|
+
"publishedNotice": {
|
|
16
|
+
"date": null,
|
|
17
|
+
"url": "https://developers.facebook.com/docs/graph-api/changelog/versions"
|
|
18
|
+
},
|
|
19
|
+
"effectiveDate": "2027-01-21",
|
|
20
|
+
"severity": "high",
|
|
21
|
+
"migrationNote": "Move the version segment to a supported version (v22.0 or later) and re-test the fields you read.",
|
|
22
|
+
"sources": ["https://developers.facebook.com/docs/graph-api/changelog/versions"],
|
|
23
|
+
"status": "verified"
|
|
24
|
+
}
|
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "quickbooks-minorversion-below-75-ignored",
|
|
3
|
+
"provider": "quickbooks",
|
|
4
|
+
"title": "Minor versions below 75 are silently answered as minor version 75",
|
|
5
|
+
"summary": "Since 2025-08-01 the QuickBooks Online Accounting API ignores any minorversion below 75 and responds with minor version 75 data, without an error. Code pinned to an older minor version receives a different response shape with no signal.",
|
|
6
|
+
"endpoint": {
|
|
7
|
+
"method": "*",
|
|
8
|
+
"path": "/v3/company/{realmId}/**"
|
|
9
|
+
},
|
|
10
|
+
"changeClass": "version-sunset",
|
|
11
|
+
"trigger": {
|
|
12
|
+
"query": [{ "name": "minorversion", "below": 75 }]
|
|
13
|
+
},
|
|
14
|
+
"firstObserved": "2025-08-01",
|
|
15
|
+
"publishedNotice": {
|
|
16
|
+
"date": null,
|
|
17
|
+
"url": "https://blogs.intuit.com/?p=34635"
|
|
18
|
+
},
|
|
19
|
+
"effectiveDate": "2025-08-01",
|
|
20
|
+
"severity": "high",
|
|
21
|
+
"migrationNote": "Set minorversion=75 (or remove it) and re-test parsing against minor version 75 responses.",
|
|
22
|
+
"sources": [
|
|
23
|
+
"https://blogs.intuit.com/?p=34635",
|
|
24
|
+
"https://www.apideck.com/blog/ai-built-accounting-integrations-maintenance",
|
|
25
|
+
"https://docs.codat.io/updates/250401-qbo-minor-versions-update"
|
|
26
|
+
],
|
|
27
|
+
"status": "verified"
|
|
28
|
+
}
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "reddit-logged-out-json-403",
|
|
3
|
+
"provider": "reddit",
|
|
4
|
+
"title": "Logged-out .json endpoints return 403",
|
|
5
|
+
"summary": "Unauthenticated requests to Reddit's public .json listing endpoints (for example /r/{subreddit}/top.json) started returning 403 Forbidden around 2026-05-30. OAuth (oauth.reddit.com) and logged-in access were reported as unaffected. No primary Reddit announcement was found.",
|
|
6
|
+
"endpoint": {
|
|
7
|
+
"method": "GET",
|
|
8
|
+
"path": "/**/*.json",
|
|
9
|
+
"hosts": ["reddit.com", "www.reddit.com", "old.reddit.com"]
|
|
10
|
+
},
|
|
11
|
+
"changeClass": "auth",
|
|
12
|
+
"trigger": {
|
|
13
|
+
"any": true
|
|
14
|
+
},
|
|
15
|
+
"firstObserved": "2026-05-30",
|
|
16
|
+
"publishedNotice": null,
|
|
17
|
+
"effectiveDate": "2026-05-30",
|
|
18
|
+
"severity": "high",
|
|
19
|
+
"migrationNote": "Move to an approved OAuth app and call oauth.reddit.com with a bearer token.",
|
|
20
|
+
"sources": [
|
|
21
|
+
"https://dev.to/tonywangca/why-reddit-blocked-unauthenticated-json-in-2026-and-how-to-still-get-reddit-data-58b9",
|
|
22
|
+
"https://bigideasdb.com/reddit-json-403-forbidden"
|
|
23
|
+
],
|
|
24
|
+
"status": "unverified"
|
|
25
|
+
}
|
|
@@ -0,0 +1,27 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "xero-accounting-transactions-scope-split",
|
|
3
|
+
"provider": "xero",
|
|
4
|
+
"title": "Broad accounting.transactions scope replaced by granular scopes",
|
|
5
|
+
"summary": "Xero split accounting.transactions into granular scopes (invoices, payments, bank transactions, manual journals, classic expenses, each with a .read variant). Apps created after 2026-03-02 must request granular scopes; existing apps keep the broad scopes until September 2027, and each connected user must re-authorize to receive the new ones.",
|
|
6
|
+
"endpoint": {
|
|
7
|
+
"method": "*",
|
|
8
|
+
"path": "/api.xro/2.0/**"
|
|
9
|
+
},
|
|
10
|
+
"changeClass": "scope-change",
|
|
11
|
+
"trigger": {
|
|
12
|
+
"any": true
|
|
13
|
+
},
|
|
14
|
+
"firstObserved": null,
|
|
15
|
+
"publishedNotice": {
|
|
16
|
+
"date": null,
|
|
17
|
+
"url": "https://devblog.xero.com/upcoming-changes-to-xero-accounting-api-scopes-705c5a9621a0"
|
|
18
|
+
},
|
|
19
|
+
"effectiveDate": "2027-09-13",
|
|
20
|
+
"severity": "medium",
|
|
21
|
+
"migrationNote": "Request the granular scopes in the authorization URL and have each connection re-authorize before the cutoff.",
|
|
22
|
+
"sources": [
|
|
23
|
+
"https://devblog.xero.com/upcoming-changes-to-xero-accounting-api-scopes-705c5a9621a0",
|
|
24
|
+
"https://www.apideck.com/blog/xero-scopes"
|
|
25
|
+
],
|
|
26
|
+
"status": "verified"
|
|
27
|
+
}
|
package/bin/shapi.js
ADDED