Skip to content

fix(evals): place a pnpm catalog's commits on their Angular major - #10

Merged
hazeliscoding merged 1 commit into
mainfrom
fix/grade-catalog-commits
Nov 8, 2026
Merged

hazeliscoding merged 1 commit into
mainfrom
fix/grade-catalog-commits

Conversation

@hazeliscoding

Copy link
Copy Markdown
Owner

Summary

The catalog case's one-commit-per-major check failed a run that did everything right. In a pnpm catalog project, package.json only says "@angular/core": "catalog:", so the grader read every commit as landing on no major. The version now comes from that commit's pnpm-workspace.yaml.

Checked

  • A new grading test reads ^21.2.0 from a catalog, past another entry and a trailing comment, and a plain package.json reads as before.
  • The run that showed it: upgrade-pnpm-catalog with the skill scored 13/14. Its one commit is "chore(deps): upgrade to Angular 21", and the catalog check on the same run found @angular/core at 21. This is the only check it failed.

In a catalog project package.json only says catalog:, so every commit read as landing on no major, and the catalog case's one-commit-per-major check failed a run that had committed Angular 21 correctly. The version now comes from the commit's pnpm-workspace.yaml.
@hazeliscoding
hazeliscoding merged commit 766d8f5 into main Nov 8, 2026
10 checks passed
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.

1 participant