Skip to content

build: account for new dev-infra packages @angular/ng-dev and @angular/build-tooling #25345

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 26, 2022

Conversation

devversion
Copy link
Member

We split the dev-infra-private packagve to decouple the ng-dev tool from
the build tooling. This allows us to easily update ng-dev e.g. in LTS
branches without needing to update Bazel.

It is important that ng-dev can be updated as much as possilbe in all
branches to ensure the release IPC reliably works.

…ular/build-tooling`

We split the dev-infra-private packagve to decouple the ng-dev tool from
the build tooling. This allows us to easily update ng-dev e.g. in LTS
branches without needing to update Bazel.

It is important that ng-dev can be updated as much as possilbe in all
branches to ensure the release IPC reliably works.
@devversion devversion marked this pull request as ready for review July 26, 2022 13:35
@devversion devversion added target: patch This PR is targeted for the next patch release merge safe labels Jul 26, 2022
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

LGTM

@devversion devversion added the action: merge The PR is ready for merge by the caretaker label Jul 26, 2022
@devversion devversion merged commit 00ee53a into angular:main Jul 26, 2022
@devversion devversion deleted the split-ng-dev branch July 26, 2022 15:05
devversion added a commit that referenced this pull request Jul 26, 2022
…ular/build-tooling` (#25345)

We split the dev-infra-private packagve to decouple the ng-dev tool from
the build tooling. This allows us to easily update ng-dev e.g. in LTS
branches without needing to update Bazel.

It is important that ng-dev can be updated as much as possilbe in all
branches to ensure the release IPC reliably works.

(cherry picked from commit 00ee53a)
devversion added a commit that referenced this pull request Jul 26, 2022
…ular/build-tooling` (#25345)

We split the dev-infra-private packagve to decouple the ng-dev tool from
the build tooling. This allows us to easily update ng-dev e.g. in LTS
branches without needing to update Bazel.

It is important that ng-dev can be updated as much as possilbe in all
branches to ensure the release IPC reliably works.

(cherry picked from commit 00ee53a)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Aug 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants