@uipath/skills 1.202.0-preview.700 → 1.202.0-preview.710
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/package.json +1 -1
- package/skills/uipath-admin/references/audit-commands.md +11 -11
- package/skills/uipath-admin/references/audit-workflow-guide.md +21 -19
- package/skills/uipath-admin/references/external-app-management.md +1 -1
- package/skills/uipath-admin/references/pat-management.md +2 -2
- package/skills/uipath-planner/assets/templates/agent-sdd-template.md +1 -1
- package/skills/uipath-planner/assets/templates/api-workflow-sdd-template.md +1 -1
- package/skills/uipath-planner/assets/templates/bpmn-sdd-template.md +1 -1
- package/skills/uipath-planner/assets/templates/coded-app-sdd-template.md +1 -1
- package/skills/uipath-planner/assets/templates/flow-sdd-template.md +1 -1
- package/skills/uipath-planner/assets/templates/rpa-sdd-template.md +1 -1
- package/skills/uipath-rpa/references/activity-docs/UiPath.AzureWVD.Activities/1.5/coded/examples.md +1 -1
- package/skills/uipath-rpa/references/activity-docs/UiPath.Word.Activities/2.5/coded/examples.md +4 -4
- package/skills/uipath-rpa/references/legacy/data-manipulation-guide.md +7 -5
- package/skills/uipath-rpa/references/legacy/testing-guide.md +1 -1
- package/version-manifest.json +1 -1
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@uipath/skills",
|
|
3
|
-
"version": "1.202.0-preview.
|
|
3
|
+
"version": "1.202.0-preview.710",
|
|
4
4
|
"description": "UiPath agent skills for Claude Code, Codex, Cursor, Copilot, Gemini and OpenCode — RPA, UI automation, UI testing, coded agents/apps/workflows, and troubleshooting. Distributed as the UiPath Claude Code plugin.",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "UiPath"
|
|
@@ -51,13 +51,13 @@ List visible audit event sources. Pass inner `id` GUIDs from `eventTargets[]` an
|
|
|
51
51
|
Run queries with filters and cursor pagination:
|
|
52
52
|
|
|
53
53
|
```bash
|
|
54
|
-
uip admin audit tenant events --from-date
|
|
54
|
+
uip admin audit tenant events --from-date <FROM_TIMESTAMP> --to-date <TO_TIMESTAMP> --limit 50 --output json
|
|
55
55
|
```
|
|
56
56
|
|
|
57
57
|
| Flag | Required | Description |
|
|
58
58
|
|---|---|---|
|
|
59
59
|
| `--from-date <iso>` | no | ISO 8601 start; inclusive. Recommended for non-trivial queries. |
|
|
60
|
-
| `--to-date <iso>` | no | ISO 8601 end; inclusive of the exact instant. Pass the next day’s start
|
|
60
|
+
| `--to-date <iso>` | no | ISO 8601 end; inclusive of the exact instant. Pass the next day’s start or `T23:59:59.999Z` to capture a full final day. Applies only to `events`; `export` bounds are whole-day inclusive, so the next-day trick over-exports. See [workflow-guide gotchas](./audit-workflow-guide.md#common-gotchas). |
|
|
61
61
|
| `--source <guid...>` | no | Repeatable event-source filter; discover IDs with `sources`. |
|
|
62
62
|
| `--target <guid...>` | no | Repeatable event-target filter. |
|
|
63
63
|
| `--type <guid...>` | no | Repeatable event-type filter. |
|
|
@@ -77,7 +77,7 @@ uip admin audit tenant events --from-date 2026-04-22T00:00:00Z --to-date 2026-04
|
|
|
77
77
|
"auditEvents": [
|
|
78
78
|
{
|
|
79
79
|
"id": "...",
|
|
80
|
-
"createdOn": "
|
|
80
|
+
"createdOn": "...",
|
|
81
81
|
"organizationId": "...",
|
|
82
82
|
"organizationName": "...",
|
|
83
83
|
"tenantId": "...",
|
|
@@ -110,14 +110,14 @@ Run the long-term audit store export for `[--from-date, --to-date]` as inclusive
|
|
|
110
110
|
|
|
111
111
|
```bash
|
|
112
112
|
uip admin audit tenant export \
|
|
113
|
-
--from-date
|
|
114
|
-
--to-date
|
|
113
|
+
--from-date <FROM_DATE> \
|
|
114
|
+
--to-date <TO_DATE> \
|
|
115
115
|
--output-path ./audit-exports \
|
|
116
116
|
--output json
|
|
117
117
|
|
|
118
118
|
uip admin audit tenant export \
|
|
119
|
-
--from-date
|
|
120
|
-
--to-date
|
|
119
|
+
--from-date <FROM_DATE> \
|
|
120
|
+
--to-date <TO_DATE> \
|
|
121
121
|
--file-format csv \
|
|
122
122
|
--output-path ./audit-exports \
|
|
123
123
|
--output json
|
|
@@ -130,7 +130,7 @@ uip admin audit tenant export \
|
|
|
130
130
|
--output json
|
|
131
131
|
```
|
|
132
132
|
|
|
133
|
-
Pass a directory, never a filename or extension. Each run creates `audit_<from>_<to>_<generated-at>`: a folder of day-wise JSON files by default or one merged CSV. JSON output is `./audit-exports/
|
|
133
|
+
Pass a directory, never a filename or extension. Each run creates `audit_<from>_<to>_<generated-at>`: a folder of day-wise JSON files by default or one merged CSV. JSON output is `./audit-exports/audit_<from>_<to>_<generatedAt>/`; CSV output is `./audit-exports/audit_<from>_<to>_<generatedAt>.csv`. The generated-at value is to the second; repeated exports do not collide.
|
|
134
134
|
|
|
135
135
|
This is the organization/tenant audit event store (LTS-schema columns such as `Identifier`, `DateCreatedUtc`, `ActorId`, `Action`, `Source`, `Category`) for compliance dumps, login history, and cross-platform “who did what where.” It is not `uip or audit-logs list --export` (the uipath-platform skill), which exports one Orchestrator tenant’s operational actions with `Component,User,Action,Operation,Time` columns. An org/tenant audit-event or compliance export with a date window and `--output-path`, whether JSON files or spreadsheet/Excel CSV, belongs here.
|
|
136
136
|
|
|
@@ -150,13 +150,13 @@ This is the organization/tenant audit event store (LTS-schema columns such as `I
|
|
|
150
150
|
|
|
151
151
|
```json
|
|
152
152
|
{
|
|
153
|
-
"Path": "C:\\absolute\\path\\to\\audit-exports\\
|
|
153
|
+
"Path": "C:\\absolute\\path\\to\\audit-exports\\audit_<from>_<to>_<generatedAt>",
|
|
154
154
|
"Format": "json",
|
|
155
155
|
"Files": 27,
|
|
156
156
|
"Bytes": 1841,
|
|
157
157
|
"Days": 31,
|
|
158
158
|
"NonEmptyDays": 27,
|
|
159
|
-
"GeneratedAt": "
|
|
159
|
+
"GeneratedAt": "<GENERATED_AT>"
|
|
160
160
|
}
|
|
161
161
|
```
|
|
162
162
|
|
|
@@ -188,7 +188,7 @@ These program-level `uip` flags appear on every command:
|
|
|
188
188
|
```json
|
|
189
189
|
{
|
|
190
190
|
"Result": "Failure",
|
|
191
|
-
"Message": "Audit export failed for
|
|
191
|
+
"Message": "Audit export failed for <DATE> (HTTP 504): Gateway Timeout",
|
|
192
192
|
"Instructions": "Ensure you are logged in with 'uip login' and have access to the audit service."
|
|
193
193
|
}
|
|
194
194
|
```
|
|
@@ -59,8 +59,8 @@ uip admin audit tenant events \
|
|
|
59
59
|
--source <ORCHESTRATOR_SOURCE_GUID> \
|
|
60
60
|
--target <FOLDERS_TARGET_GUID> \
|
|
61
61
|
--type <DELETE_FOLDER_TYPE_GUID> \
|
|
62
|
-
--from-date
|
|
63
|
-
--to-date
|
|
62
|
+
--from-date <FROM_TIMESTAMP> \
|
|
63
|
+
--to-date <TO_TIMESTAMP> \
|
|
64
64
|
--limit 50 \
|
|
65
65
|
--output json
|
|
66
66
|
```
|
|
@@ -120,12 +120,14 @@ Run:
|
|
|
120
120
|
uip admin audit org events \
|
|
121
121
|
--user-id <USER_GUID> \
|
|
122
122
|
--type <USER_LOGIN_TYPE_GUID> \
|
|
123
|
-
--from-date
|
|
124
|
-
--to-date
|
|
123
|
+
--from-date <FROM_TIMESTAMP> \
|
|
124
|
+
--to-date <TO_TIMESTAMP> \
|
|
125
125
|
--limit 200 \
|
|
126
126
|
--output json
|
|
127
127
|
```
|
|
128
128
|
|
|
129
|
+
Pass full ISO instants here: a date-only `--to-date` stops at midnight and drops the final day’s logins.
|
|
130
|
+
|
|
129
131
|
For failed logins, run:
|
|
130
132
|
|
|
131
133
|
```bash
|
|
@@ -133,8 +135,8 @@ uip admin audit org events \
|
|
|
133
135
|
--user-id <USER_GUID> \
|
|
134
136
|
--type <USER_LOGIN_TYPE_GUID> \
|
|
135
137
|
--status Failure \
|
|
136
|
-
--from-date
|
|
137
|
-
--to-date
|
|
138
|
+
--from-date <FROM_TIMESTAMP> \
|
|
139
|
+
--to-date <TO_TIMESTAMP> \
|
|
138
140
|
--output json
|
|
139
141
|
```
|
|
140
142
|
|
|
@@ -165,23 +167,23 @@ Run the applicable command:
|
|
|
165
167
|
```bash
|
|
166
168
|
# Tenant scope — most events (default json: a uniquely-named folder of day-wise JSON files under the base dir)
|
|
167
169
|
uip admin audit tenant export \
|
|
168
|
-
--from-date
|
|
169
|
-
--to-date
|
|
170
|
+
--from-date <FROM_DATE> \
|
|
171
|
+
--to-date <TO_DATE> \
|
|
170
172
|
--output-path ./audit-exports \
|
|
171
173
|
--output json
|
|
172
174
|
|
|
173
175
|
# Tenant scope as a single merged CSV (flat, Excel-friendly)
|
|
174
176
|
uip admin audit tenant export \
|
|
175
|
-
--from-date
|
|
176
|
-
--to-date
|
|
177
|
+
--from-date <FROM_DATE> \
|
|
178
|
+
--to-date <TO_DATE> \
|
|
177
179
|
--file-format csv \
|
|
178
180
|
--output-path ./audit-exports \
|
|
179
181
|
--output json
|
|
180
182
|
|
|
181
183
|
# Org scope — admin events (memberships, license, tenant lifecycle)
|
|
182
184
|
uip admin audit org export \
|
|
183
|
-
--from-date
|
|
184
|
-
--to-date
|
|
185
|
+
--from-date <FROM_DATE> \
|
|
186
|
+
--to-date <TO_DATE> \
|
|
185
187
|
--output-path ./audit-exports \
|
|
186
188
|
--output json
|
|
187
189
|
```
|
|
@@ -200,10 +202,10 @@ Typical layout:
|
|
|
200
202
|
|
|
201
203
|
```text
|
|
202
204
|
audit-exports/
|
|
203
|
-
└──
|
|
204
|
-
├──
|
|
205
|
+
└── audit_<from>_<to>_<generatedAt>/
|
|
206
|
+
├── <FROM_DATE>.json
|
|
205
207
|
├── ...
|
|
206
|
-
└──
|
|
208
|
+
└── <TO_DATE>.json
|
|
207
209
|
```
|
|
208
210
|
|
|
209
211
|
Each file is a JSON array with LTS-schema keys (`Identifier`, `DateCreatedUtc`, `OrganizationId`, `ActorId`, `User`, `Action`, …), unlike the camelCase live `events` response. Tell downstream users about this difference.
|
|
@@ -233,8 +235,8 @@ Run both scopes over a bounded recent window without filters, then summarize eve
|
|
|
233
235
|
Run:
|
|
234
236
|
|
|
235
237
|
```bash
|
|
236
|
-
uip admin audit org events --from-date
|
|
237
|
-
uip admin audit tenant events --from-date
|
|
238
|
+
uip admin audit org events --from-date <FROM_DATE> --to-date <TO_DATE> --limit 100 --output json > /tmp/org-events.json
|
|
239
|
+
uip admin audit tenant events --from-date <FROM_DATE> --to-date <TO_DATE> --limit 100 --output json > /tmp/tenant-events.json
|
|
238
240
|
```
|
|
239
241
|
|
|
240
242
|
### Step 2 — Group by event type
|
|
@@ -265,8 +267,8 @@ If multiple signals appear, run the investigations in sequence and stitch the re
|
|
|
265
267
|
|
|
266
268
|
- **Tenant context:** `tenant` commands fail without an active tenant. Re-run `uip login` with a tenant or pass `--tenant-id <guid>` on every call.
|
|
267
269
|
- **Pagination:** `next` means newer and is often null; `previous` means older. The CLI follows `previous` automatically for `--limit > 200`; do not reimplement it.
|
|
268
|
-
- **Events dates:** date-only ISO
|
|
269
|
-
- **Export dates:** bounds are inclusive whole UTC days.
|
|
270
|
+
- **Events dates:** a date-only ISO string means UTC midnight — `--from-date` given a bare `YYYY-MM-DD` resolves to `T00:00:00Z` on that day. To include the full final day, pass the day *after* the window as an exclusive `--to-date`, or give `--to-date` a full instant ending `T23:59:59.999Z`.
|
|
271
|
+
- **Export dates:** bounds are inclusive whole UTC days. A whole month is its first and last day; a single day uses the same date for both. Do not use the events next-day convention for exports.
|
|
270
272
|
- **Export lag:** the long-term store typically lags live `events` by up to 24–48 hours. Recent trailing days may be empty; offer to rerun later or end the window 2 days earlier when completeness matters.
|
|
271
273
|
- **Relative dates:** resolve them with `date -u +%F`, `date -u -d 'yesterday' +%F`, or macOS/BSD `date -u -v-1d +%F`, and echo the window.
|
|
272
274
|
- **Export schema:** default `json` writes one `<YYYY-MM-DD>.json` per UTC day in a generated folder; `--file-format csv` writes one merged CSV with the same LTS-schema field names. Both differ from live camelCase `events`; do not feed exports to a live-shape parser.
|
|
@@ -55,7 +55,7 @@ Any app with `--user-scope` requires `--redirect-uri` for authorization-code flo
|
|
|
55
55
|
|
|
56
56
|
Run the following to generate a secret; its value is shown only once:
|
|
57
57
|
```bash
|
|
58
|
-
uip admin external-apps generate-secret <CLIENT_ID> --description "Rotated secret" --expiration "
|
|
58
|
+
uip admin external-apps generate-secret <CLIENT_ID> --description "Rotated secret" --expiration "<EXPIRATION_DATE>" --output json
|
|
59
59
|
```
|
|
60
60
|
|
|
61
61
|
Confirm with the user first, then run the following to delete a secret; only the secret ID is required:
|
|
@@ -19,7 +19,7 @@ PATs provide scoped API authentication for users when user-context authenticatio
|
|
|
19
19
|
```bash
|
|
20
20
|
uip admin pat create \
|
|
21
21
|
--description "CI/CD pipeline token" \
|
|
22
|
-
--expiration "
|
|
22
|
+
--expiration "<EXPIRATION_DATE>" \
|
|
23
23
|
--scope "OR.Folders.Read,OR.Jobs.Read" \
|
|
24
24
|
--output json
|
|
25
25
|
```
|
|
@@ -44,7 +44,7 @@ uip admin pat revoke <TOKEN_ID> --output json
|
|
|
44
44
|
Run the following with a new expiration. The new token value is returned only once:
|
|
45
45
|
|
|
46
46
|
```bash
|
|
47
|
-
uip admin pat regenerate <TOKEN_ID> --expiration "
|
|
47
|
+
uip admin pat regenerate <TOKEN_ID> --expiration "<EXPIRATION_DATE>" --output json
|
|
48
48
|
```
|
|
49
49
|
|
|
50
50
|
## Error Handling
|
|
@@ -295,7 +295,7 @@ flowchart LR
|
|
|
295
295
|
|
|
296
296
|
| Connector | System | Access Method | Used By |
|
|
297
297
|
|---|---|---|---|
|
|
298
|
-
| <CONNECTOR_NAME> | <
|
|
298
|
+
| <CONNECTOR_NAME> | <SYSTEM_NAME> | <ACCESS_METHOD> | <TOOLS> |
|
|
299
299
|
|
|
300
300
|
### IXP / Document Understanding Models
|
|
301
301
|
|
|
@@ -267,7 +267,7 @@ flowchart LR
|
|
|
267
267
|
|
|
268
268
|
| Connector | System | Access Method | Used By |
|
|
269
269
|
|---|---|---|---|
|
|
270
|
-
| <CONNECTOR_NAME> | <
|
|
270
|
+
| <CONNECTOR_NAME> | <SYSTEM_NAME> | <ACCESS_METHOD> | <NODES> |
|
|
271
271
|
|
|
272
272
|
### IXP / Document Understanding Models
|
|
273
273
|
|
|
@@ -202,7 +202,7 @@ See sdd-generation-guide.md Phase 3 Step 2 item 4 for the format spec.
|
|
|
202
202
|
|
|
203
203
|
| Connector | System | Access Method | Used By |
|
|
204
204
|
|---|---|---|---|
|
|
205
|
-
| <CONNECTOR_NAME> | <
|
|
205
|
+
| <CONNECTOR_NAME> | <SYSTEM_NAME> | <ACCESS_METHOD> | <PAGES_OR_COMPONENTS> |
|
|
206
206
|
|
|
207
207
|
---
|
|
208
208
|
|
|
@@ -228,7 +228,7 @@ flowchart LR
|
|
|
228
228
|
|
|
229
229
|
| Connector | System | Access Method | Used By |
|
|
230
230
|
|---|---|---|---|
|
|
231
|
-
| <CONNECTOR_NAME> | <
|
|
231
|
+
| <CONNECTOR_NAME> | <SYSTEM_NAME> | <ACCESS_METHOD> | <NODES> |
|
|
232
232
|
|
|
233
233
|
### IXP / Document Understanding Models
|
|
234
234
|
|
|
@@ -332,7 +332,7 @@ public enum <EnumName>
|
|
|
332
332
|
|
|
333
333
|
| Connector | System | Access Method | Used By |
|
|
334
334
|
|---|---|---|---|
|
|
335
|
-
| <CONNECTOR_NAME> | <
|
|
335
|
+
| <CONNECTOR_NAME> | <SYSTEM_NAME> | <ACCESS_METHOD> | <STEPS_OR_APPS> |
|
|
336
336
|
|
|
337
337
|
### IXP / Document Understanding Models
|
|
338
338
|
|
package/skills/uipath-rpa/references/activity-docs/UiPath.AzureWVD.Activities/1.5/coded/examples.md
CHANGED
|
@@ -273,7 +273,7 @@ namespace MyProject
|
|
|
273
273
|
string[] userIds = new[]
|
|
274
274
|
{
|
|
275
275
|
"aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee", // Azure AD object ID
|
|
276
|
-
"ffffffff-
|
|
276
|
+
"ffffffff-aaaa-bbbb-cccc-dddddddddddd"
|
|
277
277
|
};
|
|
278
278
|
await roleService.AssignObjectsToApplicationGroup(appGroup, userIds);
|
|
279
279
|
Log("Users assigned to application group.");
|
package/skills/uipath-rpa/references/activity-docs/UiPath.Word.Activities/2.5/coded/examples.md
CHANGED
|
@@ -100,10 +100,10 @@ namespace MyProject
|
|
|
100
100
|
using var doc = word.UseWordDocument("form.docx");
|
|
101
101
|
|
|
102
102
|
// Fill bookmarks with data
|
|
103
|
-
doc.SetBookmarkContent("CompanyName", "
|
|
104
|
-
doc.SetBookmarkContent("Address", "
|
|
105
|
-
doc.SetBookmarkContent("ContactName", "
|
|
106
|
-
doc.SetBookmarkContent("Phone", "
|
|
103
|
+
doc.SetBookmarkContent("CompanyName", "<COMPANY_NAME>");
|
|
104
|
+
doc.SetBookmarkContent("Address", "<STREET_ADDRESS>");
|
|
105
|
+
doc.SetBookmarkContent("ContactName", "<CONTACT_NAME>");
|
|
106
|
+
doc.SetBookmarkContent("Phone", "<PHONE_NUMBER>");
|
|
107
107
|
doc.SetBookmarkContent("Date", DateTime.Now.ToString("yyyy-MM-dd"));
|
|
108
108
|
|
|
109
109
|
Log("Bookmarks populated successfully.");
|
|
@@ -15,16 +15,18 @@ Use `System.Text.RegularExpressions.Regex` for pattern matching and extraction.
|
|
|
15
15
|
| Pattern | RegEx | Match Examples |
|
|
16
16
|
|---|---|---|
|
|
17
17
|
| Email | `[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}` | `user@example.com` |
|
|
18
|
-
| Phone (US) | `\(?\d{3}\)?[-.\s]?\d{3}[-.\s]?\d{4}` | `(
|
|
19
|
-
| Date (MM/DD/YYYY) | `\d{2}/\d{2}/\d{4}` | `
|
|
20
|
-
| Date (YYYY-MM-DD) | `\d{4}-\d{2}-\d{2}` | `
|
|
18
|
+
| Phone (US) | `\(?\d{3}\)?[-.\s]?\d{3}[-.\s]?\d{4}` | `(NNN) NNN-NNNN`, `NNN.NNN.NNNN` |
|
|
19
|
+
| Date (MM/DD/YYYY) | `\d{2}/\d{2}/\d{4}` | `MM/DD/YYYY` |
|
|
20
|
+
| Date (YYYY-MM-DD) | `\d{4}-\d{2}-\d{2}` | `YYYY-MM-DD` |
|
|
21
21
|
| Currency (USD) | `\$[\d,]+\.?\d{0,2}` | `$1,234.56`, `$50` |
|
|
22
22
|
| Invoice Number | `INV-\d{4,10}` | `INV-12345`, `INV-0001234567` |
|
|
23
23
|
| ZIP Code (US) | `\d{5}(-\d{4})?` | `90210`, `90210-1234` |
|
|
24
|
-
| SSN | `\d{3}-\d{2}-\d{4}` | `
|
|
24
|
+
| SSN | `\d{3}-\d{2}-\d{4}` | `NNN-NN-NNNN` |
|
|
25
25
|
| IP Address | `\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}` | `192.168.1.1` |
|
|
26
26
|
| Decimal Number | `-?\d+\.?\d*` | `123.45`, `-67`, `0.5` |
|
|
27
27
|
|
|
28
|
+
> `N` marks a digit position. Examples for personally identifiable patterns are masked, not literal values.
|
|
29
|
+
|
|
28
30
|
### VB.NET Usage
|
|
29
31
|
|
|
30
32
|
```vb
|
|
@@ -376,7 +378,7 @@ CDbl("1,234.56") ' Works on US locale, fails on German locale (1.234,56)
|
|
|
376
378
|
Double.Parse("1,234.56", System.Globalization.CultureInfo.InvariantCulture)
|
|
377
379
|
|
|
378
380
|
' SAFE: explicit date format
|
|
379
|
-
DateTime.ParseExact(
|
|
381
|
+
DateTime.ParseExact(dateText, "MM/dd/yyyy", System.Globalization.CultureInfo.InvariantCulture)
|
|
380
382
|
```
|
|
381
383
|
|
|
382
384
|
### Common Conversion Traps
|
|
@@ -111,7 +111,7 @@ Sequence "Test_ValidateInput_MultipleScenarios"
|
|
|
111
111
|
| `"INV-12345"` | True | Valid invoice number |
|
|
112
112
|
| `""` | False | Empty string |
|
|
113
113
|
| `"INV"` | False | Incomplete format |
|
|
114
|
-
| `"INV-
|
|
114
|
+
| `"INV-"` + 11 digits | False | Number too long |
|
|
115
115
|
| `"inv-12345"` | True | Lowercase (should be case-insensitive) |
|
|
116
116
|
|
|
117
117
|
### Data Sources
|
package/version-manifest.json
CHANGED