You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rename validation command in package.json from validate-all to validate-files for clarity. Update README.md to reflect the new command and provide additional context on the validation process. Modify GitHub Actions workflow to clarify that changes to registry.json won't trigger the build workflow, preventing infinite loops. (#16)
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -312,13 +312,13 @@ Validate the aggregated registry (requires registry.json to exist - run `npm run
312
312
npm run validate
313
313
```
314
314
315
-
Validate everything (schemas, plugins, and existing registry.json if present):
315
+
Validate existing files (schemas, plugins, and registry.json if present):
316
316
317
317
```bash
318
318
npm run validate-files
319
319
```
320
320
321
-
This runs: `validate-schemas` → `validate-plugins` → `validate` (skips registry validation if registry.json doesn't exist)
321
+
This runs: `validate-schemas` → `validate-plugins` → `validate` (skips registry validation if registry.json doesn't exist). Note: This does not build the registry - run `npm run build` first if you need to generate registry.json.
0 commit comments