Skip to content

Add ALCHEMI Toolkit to the product enum - #852

Merged
siqinvidia merged 1 commit into
mainfrom
moshea/add-alchemi-product
Nov 9, 2026
Merged

siqinvidia merged 1 commit into
mainfrom
moshea/add-alchemi-product

Conversation

@mosheabr

@mosheabr mosheabr commented Nov 9, 2026

Copy link
Copy Markdown
Collaborator

Adds ALCHEMI Toolkit to the product.primary enum. The metadata regen has been failing on the new nvalchemi-toolkit skill (#851) because no matching product value exists. The value matches the name in components.d/alchemi-toolkit.yml, so no registry change is needed.

Generated files will update in the next metadata regeneration.

🤖 Generated with Claude Code

Signed-off-by: Moshe Abramovitch <moshea@nvidia.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@siqinvidia siqinvidia left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed at 847b2f4. This adds only ALCHEMI Toolkit to the product.primary schema enum, matching the existing component name. Verified that the generator now derives that exact product deterministically (previously None), JSON Schema validation passes, and existing metadata failure/product-mapping regression tests all pass. DCO, Authors, Content Integrity and NVSkills CI gate pass. The metadata check fails only on benchmarks.json awaiting aggregation following #849; regeneration after this schema fix will produce the downstream generated files.

@siqinvidia
siqinvidia merged commit 5b5f45c into main Nov 9, 2026
7 of 8 checks passed
@siqinvidia
siqinvidia deleted the moshea/add-alchemi-product branch November 9, 2026 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants