build: introduce package deprecation metadata and integrate it into the release configuration#32675
Conversation
alan-agius4
added
action: review
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
alan-agius4
force-pushed
the
deprecate-architect-cli
branch
from
d8f9492 to
7c2243c
Compare
…he release configuration `ng-dev` now supports deprecations of NPM packages. See: angular/dev-infra#3463
alan-agius4
force-pushed
the
deprecate-architect-cli
branch
from
7c2243c to
383871a
Compare
angular-robot
bot
added
the
area: build & ci
|
/gemini review |
There was a problem hiding this comment.
Code Review
The pull request introduces support for package deprecation metadata, integrating it into the release configuration. This involves updating the .monorepo.json schema to include a deprecated field, modifying the PackageInfo interface in scripts/packages.mts to reflect this new property, and ensuring the deprecated information is correctly propagated through the release.mjs configuration. The changes are well-structured and correctly implement the new metadata.
alan-agius4
added
action: merge
|
This PR was merged into the repository. The changes were merged into the following branches:
|
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
2 participants
ng-devnow supports deprecations of NPM packages. See: angular/dev-infra#3463