feat(monorepo): group ng-packagr with angular-cli

[aqeelat]

Changes

Add ng-packagr to the angular-cli monorepo group by converting the repoGroups entry from a string to an array, matching the existing pattern used by aspire, algolia-instantsearch, and others.

Context

• This doesn't close an Issue, but I accept the risk that this PR may be closed if maintainers disagree with its opening or implementation

ng-packagr is the official Angular library compiler. It follows the Angular CLI release cycle — same major versions, same upgrade cadence — but lives in a separate repository (ng-packagr/ng-packagr). Without this change, Renovate creates separate PRs for Angular CLI and ng-packagr updates, which then need to be upgraded and tested together manually.

AI assistance disclosure

• Yes — substantive assistance. This PR was written by an AI agent (GLM-5.2 via opencode). The change was identified and implemented by the agent at the user's direction.

Documentation

• No documentation update is required

How I've tested this work

• Code inspection only

The monorepo preset spec (monorepos.spec.ts) only validates preset name format, not individual group entries. The JSON schema for repoGroups explicitly allows arrays of URIs, and several existing entries already use arrays.

[github-actions]

Hi there,
When adding a new monorepo to the monorepo.json, please note that:

• Any dependency update(s) from this monorepo will be upgraded in a single PR
• If the dependencies are not all versioned identically (i.e. they're all at 16.0.5 and a release in one requires all being updated) this will lead to Immortal PRs
  • This is not be the intended behaviour, and is generally not recommended by Renovate maintainers. We only accept it if the packages strictly need to be updated together.

It is worth both the author of the PR and the reviewer confirming that this is the intended behaviour.