feat: derive batch PR titles and commit messages from changelog entries

[gjtorikian]

Summary

Every generated SDK PR in a batch shared the same contentless title — feat(generated): OrganizationMembership (batch e471ddef) — language-independent and saying nothing about what changed.

scripts/open-batch-pr.mjs now derives the title from the classify entries (the same summaries that go into the release-note fragment), e.g. feat(generated): Added roles to organization membership models (+2 more):

• rollupPrefix() mirrors the changelog rollup (feat! → feat(generated)!, else feat → feat(generated), else fix/chore), so the title keeps a valid conventional-commit prefix and the SDK repos' lint_pr_title / "Validate PR title" check still passes.
• entriesSummary() uses the lead entry's summary plus (+N more).
• With zero entries it falls back to the previous feat(generated): <services> (batch <id>) form.

The catch-all commit message is now chore(generated): regenerate shared files for <services> (the per-entry commits already used the descriptive entry headlines).

Test plan

• node --test scripts/__tests__/open-batch-pr.spec.mjs — updated + new cases: single entry, multiple entries with (+N more), zero-entries fallback, feat!/feat/fix rollup ordering, a regex assertion that every produced title keeps a valid conventional prefix, the new catch-all message, and a --dry-run end-to-end asserting the gh pr create title is entry-derived.
• Full npm test: 41 pass, 0 fail.

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR makes generated SDK batch PRs and commits more descriptive. The main changes are:

• PR titles now come from classified changelog entries when available.
• Malformed or empty entries fall back to the old batch title.
• Catch-all generated commits now include the affected services.
• Tests cover title rollups, fallback behavior, dry-run output, and commit messages.
• Development dependencies were bumped.

Confidence Score: 3/5

The title and commit-message behavior is covered, but the dependency override can affect the Postman generation runtime path.

• The changed script behavior is focused and covered by targeted tests for entry-derived titles, fallback titles, rollup prefixes, dry-run output, and catch-all commit messages.
• The package override changes dependency resolution beyond the script being modified, which can affect a transitive converter used by the Postman generation command.
• The remaining risk is isolated to dependency resolution around js-yaml and openapi-to-postmanv2 rather than the PR title derivation logic.

package.json

T-Rex Logs

What T-Rex did

• The base run of the batch-pr-title tests was executed and showed the old generic dry-run title coverage along with the 13-test suite passing.
• The head run of the same focused test file was executed and showed 19 passing tests, including descriptive dry-run title derivation and new catch-all commit message assertions.
• A base direct probe was executed to inspect title generation and export behavior, showing that the generic fallback title was produced and catchAllMessage was not exported.
• A head direct probe was executed to inspect the updated title and commit-message coverage, revealing multiple generated tag variants (feat(generated), feat(generated)!, fix(generated), (+N more)), zero-entry and malformed fallbacks, and the generated chore line 'chore(generated): regenerate shared files for Vault, SSO'.

_{Ran code and verified through T-Rex}

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
package.json:58
**Transitive YAML Version Breakage**

Changing the `js-yaml` override to `^5.1.0` forces transitive consumers onto the new major version too. The Postman generation path uses `openapi-to-postmanv2@6.1.0`, which declares its own `js-yaml` dependency in the lockfile; if that converter relies on the v4 package shape or APIs, `npm run generate:postman` can fail at runtime even though this repo's direct `yaml.load()` call still type-checks.

_{Reviews (3): Last reviewed commit: "chore: update deps" | Re-trigger Greptile}

[greptile-apps]

Transitive YAML Version Breakage

Changing the js-yaml override to ^5.1.0 forces transitive consumers onto the new major version too. The Postman generation path uses openapi-to-postmanv2@6.1.0, which declares its own js-yaml dependency in the lockfile; if that converter relies on the v4 package shape or APIs, npm run generate:postman can fail at runtime even though this repo's direct yaml.load() call still type-checks.

Prompt To Fix With AI

This is a comment left during a code review.
Path: package.json
Line: 58

Comment:
**Transitive YAML Version Breakage**

Changing the `js-yaml` override to `^5.1.0` forces transitive consumers onto the new major version too. The Postman generation path uses `openapi-to-postmanv2@6.1.0`, which declares its own `js-yaml` dependency in the lockfile; if that converter relies on the v4 package shape or APIs, `npm run generate:postman` can fail at runtime even though this repo's direct `yaml.load()` call still type-checks.

How can I resolve this? If you propose a fix, please make it concise.